Downloaded 27 times
![#tarabica15
Let’s update a row!
What do we need?
USE AdventureWorks2012
GO
UPDATE [Person].[Address]
SET AddressLine1=’Belgrade, Serbia'
WHERE AddressID=2
S
IX
Header
Row
Row
Row
Row
Row
IX
X](https://image.slidesharecdn.com/slidedeckfinal-150328062657-conversion-gate01/75/The-Nightmare-of-Locking-Blocking-and-Isolation-Levels-12-2048.jpg)
Uploaded byBoris Hristov
The Nightmare of Locking, Blocking and Isolation Levels!
The document presents an overview of locking, blocking, and transaction isolation levels in SQL Server, emphasizing the importance of understanding concurrency control methods. It outlines the different types of locks, compatibility, and escalation, as well as troubleshooting techniques for locking problems. Additionally, it discusses various transaction isolation levels and their impact on data consistency and concurrency, advising careful consideration in choosing isolation levels.
More Related Content
![[Altibase] 6 what is the mvcc](https://cdn.slidesharecdn.com/ss_thumbnails/altibase6whatisthemvcc-160126071035-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to The Nightmare of Locking, Blocking and Isolation Levels!
The Nightmare of Locking, Blocking and Isolation Levels!
- 1.
- 2. #tarabica15 Boris Hristov SQL ServerConsultant and Trainer Welcome to the nightmare of locking, blocking and isolation levels!
- 3.
- 4.
- 5. #tarabica15 Agenda… Locks. What isthere for us? Troubleshooting locking problems Transaction Isolation Levels
- 6. #tarabica15 Locks. What isthere for us?
- 7. #tarabica15 Methods of ConcurrencyControl 1. Pessimistic – SQL Server uses locks, causes blocks and who said deadlocks? 2. Optimistic – SQL Server generates versions for everyone, but the updates…
- 8. #tarabica15 What Are Locksand what is locking? Lock – internal memory structure that “tells” us what we all do with the resources inside the system Locking – mechanism to protect the resources and guarantee consistent data
- 9. #tarabica15 Intent Used for: Preventingincompatible locks Duration: End of the transaction Shared (S) Used for: Reading Duration: Released almost immediately (depends on the isolation level) Update (U) Used for: Preparing to modify Duration: End of the transaction or until converted to exclusive (X) Exclusive (X) Used for: Modifying Duration: End of the transaction Common Lock Types
- 10. #tarabica15 Lock Compatibility Not alllocks are compatible with other locks. Lock Shared Update Exclusive Shared (S) X Update (U) X X Exclusive (X) X X X
- 11.
- 12. #tarabica15 Let’s update arow! What do we need? USE AdventureWorks2012 GO UPDATE [Person].[Address] SET AddressLine1=’Belgrade, Serbia' WHERE AddressID=2 S IX Header Row Row Row Row Row IX X
- 13. #tarabica15 Methods to ViewLocking Information Dynamic Management Views SQL Server Profiler or Extended Events Performance Monitor or Activity Monitor
- 14.
- 15. #tarabica15 Locking and blocking Lockingand blocking are often confused! Locking • The action of taking and potentially holding locks • Used to implement concurrency control Blocking is result of locking! • One process needs to wait for another process to release locked resources • In a multiuser environment, there is always, always blocking! • Only a problem if it lasts too long
- 16.
- 17. #tarabica15 Controlling Lock Escalation 1.Switch the escalation level (per table) AUTO – Partition-level escalation if the table is partitioned TABLE – Always table-level escalation DISABLE – Do not escalate until absolutely necessary 2. Just disable it (that’s not Nike’s “Just do it!”) • Trace flag 1211 – disables lock escalation on server level • Trace flag 1224 – disables lock escalation if 40% of the memory used is consumed SELECT lock_escalation_desc FROM sys.tables WHERE name = 'Person.Address' ALTER TABLE Person.Address SET (LOCK_ESCALATION = {AUTO | TABLE | DISABLE}
- 18. #tarabica15 What Are Deadlocks? TaskA Task B Resource 1 Resource 2 Who is victim? • Cost for Rollback • Deadlock priority – SET DEADLOCK_PRIORITY
- 19. #tarabica15 1. Keep thetransactions as short as possible 2. No user interactions required in the middle of the transaction 3. Use indexes (proper ones) 4. Consider a server to offload some of the workloads 5. Choose isolation level Resolving blocking a.k.a live locking
- 20. #tarabica15 DEMO Monitor for lockswith xEvents Lock escalation – both to table and partition Deadlock and the SET DEADLOCK_PRIORITY option
- 21.
- 22. #tarabica15 SET TRANSACTION ISOLATIONLEVEL READ UNCOMMITTED (NOLOCK?) Transaction 1 Transaction 2 Suggestion: Better offload the reads or go with optimistic level concurrency! Select Update eXclusive lock Read Uncommitted (pessimistic concurrency control) Dirty read
- 23. #tarabica15 SET TRANSACTION ISOLATIONLEVEL REPEATABLE READ Transaction 1 S(hared) lock select No non-repeatable reads possible (updates during Transaction 1) Phantom records still possible (inserts during Transaction 1) Update Transaction 2 Repeatable Read (pessimistic concurrency control)
- 24. #tarabica15 Transaction 1 S(hared)lock select Even phantom records are not possible! Highest pessimistic level of isolation, lowest level of concurrency Insert Transaction 2 Serializable (pessimistic concurrency control) SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
- 25. #tarabica15 Based on Rowversioning (stored inside tempdb’s version store area) • No dirty, non-repeatable reads or phantom records • Every single modification is versioned even if not used • Adds 14 bytes per row Readers do not block writers and writers do not block readers Writers can and will block writers, this can cause conflicts Optimistic Concurrency
- 26. #tarabica15 RCSI – ReadCommitted Snapshot Isolation Level • Statement level versioning • Requires ALTER DATABASE SET READ_COMMITTED_SNAPSHOT ON Snapshot Isolation Level • Transaction level versioning • Requires ALTER DATABASE SET ALLOW_SNAPSHOT_ISOLATION ON • Requires SET TRANSACTION ISOLATION LEVEL SNAPSHOT RCSI and SI (optimistic concurrency control) V1 V2 Transaction 1 Transaction 2 Select in RCSISelect Select in SI
- 27. #tarabica15 DEMO Playing around withthe Isolation levels
- 28. #tarabica15 Summary 1. Blocking issomething normal when it’s not for long 2. There are numerous of ways to monitor locking and blocking 3. Be extremely careful for lock escalations 4. Choosing the Isolation level is also a business decision!
- 29. #tarabica15 Resources MCM Readiness videoson locking lecture and demo MCM Readiness video on Snapshot Isolation Level http://blogs.msdn.com/b/bartd/archive/tags/sql+locking http://www.sqlskills.com/blogs/paul/category/locking/ Lock hints - http://www.techrepublic.com/article/control- sql-server-locking-with-hints/5181472
- 30.