The document discusses various SQL isolation levels including optimistic and pessimistic concurrency, with a focus on their impact on transactions, locking mechanisms, and potential conflicts. It details the types of locks (shared, update, exclusive) and their compatibility in the context of database operations, along with methods to monitor locking information. The importance of choosing appropriate isolation levels for business decisions and application performance is emphasized.

1. DEEP INTO
ISOLATION LEVELS
Boris Hristov
SQLBits, Superheroes, 2015

2. That’s not a Hekaton Talk!
(In-Memory OLTP)

3. So who am I?
@BorisHristov

4. Isolation Levels time
complexity
Fundamentals
?
Session’s Timeline

5. The Fundamentals

6. Pessimistic Concurrency Optimistic Concurrency
Locks
Blocking
Versions
Version Store
Update Conflicts
Locks
Locking
Blocking
Deadlocks
Lock Escalations

7. Common lock types
Intent
Used for: Preventing incompatible 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

8. Lock Compatibility
Lock Shared Update Exclusive
Shared (S)
  X
Update (U)
 X X
Exclusive (X)
X X X

9. Lock Hierarchy
Database
Table
Page
Row

10. Let’s update a row. What do we need?
USE AdventureWorks2012
GO
UPDATE [Person].[Address]
SET AddressLine1=‘London, UK'
WHERE AddressID=2
S
IX
Header
Row
Row
Row
Row
Row
IX
X
A query! 

11. Methods to View Locking Information
Dynamic
Management
Views
SQL Server
Profiler or
Extended Events
Performance
monitor or Activity
Monitor

12. DEMO
Locking and Locking Hierarchies

13. Transaction isolation levels
(pessimistic concurrency)

14. SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED (NOLOCK?)
Transaction 1
Transaction 2
Suggestion: Better offload the reads or go with optimistic level concurrency!
Select
Update
eXclusive lock
Read Uncommitted
(pessimisticconcurrencycontrol)
Dirty read

15. SET TRANSACTION ISOLATION LEVEL READ COMMITTED
Transaction 1 rows
Non-repeatable reads possible (updates during Transaction 1)
Phantom records possible (inserts during Transaction 1)
What else? (that’s a Pluralsight voucher right here!)
Updates and Inserts
Transaction 2
Read Committed
(pessimisticconcurrencycontrol)
S
S
S
S

16. SET TRANSACTION ISOLATION LEVEL 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
(pessimisticconcurrencycontrol)

17. Transaction 1 S(hared) lock
select
Even phantom records are not possible!
Highest pessimistic level of isolation, lowest level of concurrency
Oh, yeah, TransactionScope in C# and MSDTC transactions default to this level too
Insert
Transaction 2
Serializable
(pessimisticconcurrencycontrol)
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE

18. DEMO
Playing with Isolation levels (Pessimistic Concurrency)

19. Transaction isolation levels
(optimistic concurrency)

20. Read Committed and Snapshot Isolation levels
 RCSI – Read Committed 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
V1 V2
Transaction 1
Transaction 2
Select in RCSISelect
Select in SI

21. DEMO
Playing with Isolation levels (Optimistic Concurrency)
… and Azure DB
too

22. Just before we end…

23. Isolation levels can have dramatic impact on your application
As such, isolation levels must also be a business decision
The behavior of the readers changes in the various levels
Writers, though, will always block. No matter what!
And one more thing – please be careful with ORMs 
Summary

24. Thank you!
Contacts:
brshristov@live.com
www.borishristov.com
@BorisHristov