60 likes | 160 Views
Locking Internals By Amit R S Bansal Director, Principal Consultant & Trainer www.PeoplewareIndia.com | www.amitbansal.net MVP, MCT, MCTS , MCITP etc .. www.facebook.com/groups/theSQLGeeks Follow me on twitter now @ A_Bansal http :// www.facebook.com/amit.r.bansal. Amit R S Bansal.
E N D
Locking Internals By Amit R S Bansal Director, Principal Consultant & Trainer www.PeoplewareIndia.com | www.amitbansal.net MVP, MCT, MCTS, MCITP etc.. www.facebook.com/groups/theSQLGeeks Follow me on twitter now @A_Bansal http://www.facebook.com/amit.r.bansal
Amit R S Bansal Technical Director, eDominer Systems & Peopleware India Corporate Trainer/Consultant & Evangelist Conducted more than 450+ workshops on SQL Server & BI for top notch IT companies world wide Microsoft MVP for SQL Server Speaker at TechED India, TechED US & TechEDEurope Speaking at SQLBITs this March in London Technical Reviewer/SME – MSL courses & certifications on SQL Server Founder & President – SQLServerGeeks.com
Locking Myths debunked • Lock escalation • Row/Page -> Table (default) or • Row/Page -> Partition (if table is partitioned and partition-level locking is enabled) • Never from Row -> Page • & Never from Partition -> Table • Update Locks • TRAN A is locking rec1. TranB wants to update rec1, rec2 & rec3. • TRANB will wait for an U lock on rec1, but will not lock rec2 & rec3 (thus increasing concurrency) • PAGE locks • Mysterious (watch the demo)
Continue your learning… Be a member - www.SQLServerGeeks.com www.FaceBook.com/SQLServerGeeks Twitter @SQLServerGeeks Presentation & Scripts uploaded on www.SQLServerGeeks.com/files
Connect with Amit Bansal • www.AmitBansal.net • LinkedIN, FB, Twitter, GuestBook • Twitter: @A_Bansal • Join my network • Personal Site – http://www.amitbansal.net • LinkedIn – http://www.linkedin.com/in/AmitBansal2010 • Forum – www.FaceBook.com/groups/theSQLGeeks • FaceBook – http://www.facebook.com/people/Amit.R.Bansal • Twitter – http://www.twitter.com/A_Bansal • Blog – www.SQLServerGeeks.com
Thank you for suggestions, please email at admin@SQLServerGeeks.com