Consider the below scenario :
I have a huge table where records are present based on organizations [org_id]
Each org can have multiple records.
Now I want to delete records for more than 1 org , and the way I want to delete is through different sessions,
1 session per org.
Will this cause a deadlock ?
The way I understand is, SQL Server will escalate row locks to table locks if the number of records to be deleted is huge.
Now in my case, 1 org may have huge number of records, while the others may not have that many .
Is there a chance of getting into a table lock here , and the other 2 sessions have to wait till the table lock is release ?