GilaMonster (12/26/2012)
Sean Lange (12/26/2012)
The locking you are seeing is because of lock escalation.It's not lock escalation.
Truncate table locks at the table level because there's no other sensible level to lock at (and iirc it takes an Sch-M lock too)
Lock escalation would be if the truncate first started taking row or page locks, got over the threshold and converted the locks to table
Thanks for the correction Gail. I knew the locking was at the table level but my incorrect terminology certainly made it unclear. :w00t:
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/