Monday, March 05, 2012 5:31 PM
I have had a look in the forums but none of these quite explain what I am seeing. I am getting range S-S and Range I-N locks on indexes on numerous tables.
The scripts that are called do not have (HOLDLOCK) and are not called by a SERIALIZABLE transaction but yet still hold the range locks. I know that there are instances where a lock will escalate but I can not see why this would occur in this instance
Thanks in advance
- Changed Type Naomi NMicrosoft Community Contributor, Moderator Monday, March 05, 2012 5:34 PM Question rather than discussion
Monday, March 05, 2012 6:23 PMModerator
Are you deleting from a parent table, where the children are using CASCADE option on the foreign key constraints?
Conor vs. Isolation Level Upgrade on UPDATE/DELETE Cascading RI
- Marked As Answer by Kalman TothMicrosoft Community Contributor, Moderator Friday, April 13, 2012 6:46 PM
Monday, March 05, 2012 9:23 PM
Looks like they don't have to be running in SERIALIZABLE...
- Marked As Answer by Kalman TothMicrosoft Community Contributor, Moderator Friday, April 13, 2012 6:45 PM
Wednesday, March 07, 2012 9:25 AM
Unfortunately not but thanks for the response
Tuesday, April 10, 2012 9:11 AMMany thanks for your response Kev