Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

READ_COMMITTED_SNAPSHOT & TRUNCATE TABLE Expand / Collapse
Author
Message
Posted Friday, December 21, 2012 3:45 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, July 1, 2014 3:04 AM
Points: 16, Visits: 220
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
Post #1399620
Posted Wednesday, December 26, 2012 7:31 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 10:03 AM
Points: 12,923, Visits: 12,344
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 Moden's splitter.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs
Understanding and Using APPLY (Part 1)
Understanding and Using APPLY (Part 2)
Post #1400243
Posted Wednesday, December 26, 2012 1:04 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 10:05 AM
Points: 39,879, Visits: 36,226
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1400349
Posted Wednesday, December 26, 2012 1:07 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 10:03 AM
Points: 12,923, Visits: 12,344
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.


_______________________________________________________________

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 Moden's splitter.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs
Understanding and Using APPLY (Part 1)
Understanding and Using APPLY (Part 2)
Post #1400351
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse