December 21, 2012 at 3:45 pm
Hi,
when I use the READ_COMMITTED_SNAPSHOT and use DELETE FROM table the other session is not locked when SELECTING data.
However when I use TRUNCATE TABLE it does block the other session SELECTING data.
The difference I see is that the TRUNCATE does a X lock on PAGE level and the DELETE an IX on PAGE level.
So I know not to use TRUNCATE in such scenario, but I would like to understand what is different internally.
Kind Regards
Geoffrey
December 26, 2012 at 7:31 am
geoffrey crombez (12/21/2012)
Hi,when I use the READ_COMMITTED_SNAPSHOT and use DELETE FROM table the other session is not locked when SELECTING data.
However when I use TRUNCATE TABLE it does block the other session SELECTING data.
The difference I see is that the TRUNCATE does a X lock on PAGE level and the DELETE an IX on PAGE level.
So I know not to use TRUNCATE in such scenario, but I would like to understand what is different internally.
Kind Regards
Geoffrey
The difference in what those two statements do. Delete simply deletes rows where a truncate removes the pages. The locking you are seeing is because of lock escalation. A truncate will lock the entire table because all of the pages are being removed. Of course truncate is a lot faster because of the minimal logging involved so the locking should be very short.
_______________________________________________________________
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/
December 26, 2012 at 1:04 pm
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
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 26, 2012 at 1:07 pm
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/
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply