<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss Content Posted by Steve Jones
»
Lock Escalation
24 posts, Page 1 of 3
1
2
3
»
»»
Lock Escalation
Rate Topic
Display Mode
Topic Options
Author
Message
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Tuesday, May 24, 2011 11:15 PM
SSC-Dedicated
Group: Administrators
Last Login: Yesterday @ 5:09 AM
Points: 31,526,
Visits: 13,864
Comments posted to this topic are about the item
Lock Escalation
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #1114515
Koen Verbeeck
Koen Verbeeck
Posted Tuesday, May 24, 2011 11:31 PM
SSCrazy Eights
Group: General Forum Members
Last Login: 2 days ago @ 6:30 AM
Points: 9,410,
Visits: 6,495
Great question, learned something today.
How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
Member of
LinkedIn
. My blog at
LessThanDot
.
MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1114518
hakan.winther
hakan.winther
Posted Wednesday, May 25, 2011 12:36 AM
SSCrazy
Group: General Forum Members
Last Login: Monday, May 06, 2013 5:31 AM
Points: 2,226,
Visits: 438
I knew the answer, but I havent thought about that this is a good reason to use partitioning.
/Håkan Winther
MCITP:Database Developer 2008
Post #1114531
paul s-306273
paul s-306273
Posted Wednesday, May 25, 2011 2:23 AM
Ten Centuries
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 9:12 AM
Points: 1,167,
Visits: 646
I went for 'table' escalation only.
Maybe I should have guessed 'partition' as well...
Nice question though.
Post #1114563
mohammed moinudheen
mohammed moinudheen
Posted Wednesday, May 25, 2011 2:35 AM
SSCrazy
Group: General Forum Members
Last Login: Monday, June 17, 2013 10:29 PM
Points: 2,178,
Visits: 3,599
I thought row level locks would be escalated to table locks only.
I referred the link provided in the answer, but couldn't find any information regarding escalation to partition.
The Database Engine does not escalate row or key-range locks to page locks, but escalates them directly to table locks. Similarly, page locks are always escalated to table locks. In SQL Server 2008, locking of partitioned tables can escalate to the HoBT level for the associated partition instead of to the table lock. A HoBT-level lock does not necessarily lock the aligned HoBTs for the partition.
Did anyone find more information regarding the escalation of row level locks to partition in the link provided?
Mohammed Moinudheen
Post #1114565
Richard Warr
Richard Warr
Posted Wednesday, May 25, 2011 3:04 AM
SSCommitted
Group: General Forum Members
Last Login: Yesterday @ 4:16 AM
Points: 1,635,
Visits: 1,155
mohammed moinudheen (5/25/2011)
I thought row level locks would be escalated to table locks only.
I referred the link provided in the answer, but couldn't find any information regarding escalation to partition.
The Database Engine does not escalate row or key-range locks to page locks, but escalates them directly to table locks. Similarly, page locks are always escalated to table locks. In SQL Server 2008, locking of partitioned tables can escalate to the HoBT level for the associated partition instead of to the table lock. A HoBT-level lock does not necessarily lock the aligned HoBTs for the partition.
Did anyone find more information regarding the escalation of row level locks to partition in the link provided?
I inferred it from the same paragraph that you quoted. If a row lock can escalate to a table lock, and a table lock can escalate to a partition lock then a row lock can cause a partition lock.
Post #1114580
michael.kaufmann
michael.kaufmann
Posted Wednesday, May 25, 2011 3:04 AM
Ten Centuries
Group: General Forum Members
Last Login: Tuesday, May 28, 2013 1:34 AM
Points: 1,263,
Visits: 1,080
mohammed moinudheen (5/25/2011)
I thought row level locks would be escalated to table locks only.
I referred the link provided in the answer, but couldn't find any information regarding escalation to partition.
The Database Engine does not escalate row or key-range locks to page locks, but escalates them directly to table locks. Similarly, page locks are always escalated to table locks. In SQL Server 2008, locking of partitioned tables can escalate to the HoBT level for the associated partition instead of to the table lock. A HoBT-level lock does not necessarily lock the aligned HoBTs for the partition.
Did anyone find more information regarding the escalation of row level locks to partition in the link provided?
I'll give it a try (in a technically simplified way): The HoBT level (HoBT = Heap or B-Tree, see
http://technet.microsoft.com/en-us/library/ms189849.aspx
) is the structure underlying a table. If the table is not partitioned, you could say HoBT(a) = table(a).
For a partitioned table, each partition is one HoBT, or HoBT(a1) = p(1)table(a), HoBT(a2) = p(2)table(a), etc.
So locking just one HoBT of a partitioned table = locking the partition, but not the entire table.
Or as BOL puts it:
A HoBT-level lock does not necessarily lock the aligned HoBTs for the partition.
Personally I'd rephrase that to:
A HoBT-level lock does not necessarily lock all aligned HoBTs for an entire partitioned table.
Regards,
Michael
Post #1114581
mohammed moinudheen
mohammed moinudheen
Posted Wednesday, May 25, 2011 3:14 AM
SSCrazy
Group: General Forum Members
Last Login: Monday, June 17, 2013 10:29 PM
Points: 2,178,
Visits: 3,599
Thank you Michael and Richard. It is clear to me now
Mohammed Moinudheen
Post #1114585
L' Eomot Inversé
L' Eomot Inversé
Posted Wednesday, May 25, 2011 3:15 AM
SSCertifiable
Group: General Forum Members
Last Login: Yesterday @ 12:10 PM
Points: 7,185,
Visits: 7,285
Nice question.
But "partition" locks? Surely Heap locks, B-Tree locks (HoBT locks for short)? I don't think the term "partition lock" occurs anywhere in BoL for SQL 2008 R2.
Tom
Is minic a gheibheann béal oscailte dorn dúnta.
Is minig a cheapas beul fosgailte dòrn dùinte.
http://es.linkedin.com/in/tomthomsonsoftware
Post #1114586
mohammed moinudheen
mohammed moinudheen
Posted Wednesday, May 25, 2011 3:20 AM
SSCrazy
Group: General Forum Members
Last Login: Monday, June 17, 2013 10:29 PM
Points: 2,178,
Visits: 3,599
I'll give it a try (in a technically simplified way): The HoBT level (HoBT = Heap or B-Tree, see
http://technet.microsoft.com/en-us/library/ms189849.aspx
) is the structure underlying a table. If the table is not partitioned, you could say HoBT(a) = table(a).
For a partitioned table, each partition is one HoBT, or HoBT(a1) = p(1)table(a), HoBT(a2) = p(2)table(a), etc.
So locking just one HoBT of a partitioned table = locking the partition, but not the entire table.
Or as BOL puts it:
A HoBT-level lock does not necessarily lock the aligned HoBTs for the partition.
Personally I'd rephrase that to:
A HoBT-level lock does not necessarily lock all aligned HoBTs for an entire partitioned table.
Regards,
Michael
Excellent explanation really, easy to follow. May be you should add this in that MSDN link
Mohammed Moinudheen
Post #1114589
« Prev Topic
|
Next Topic »
24 posts, Page 1 of 3
1
2
3
»
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
