ACID in SQL Server: what it is, how it works, and how to live more adventurously.
summary
Covers ACID in SQL Server with hands-on demos: shows read uncommitted (NOLOCK) producing dirty reads, contrasts read committed, repeatable read and serializable range locks with blocking and phantom examples, and explains snapshot vs RCSI and update-conflict behavior. Reproduces a surprising merge deadlock caused by shared-range lock upgrades and resolves it by removing HOLDLOCK (falling back to read committed). Ends with how transaction log hardening, delayed durability, and tempdb versioning affect durability and recovery.
AI-written summary · about
chapters (13)
- 0:00ACID overview
- 1:12ACID in SQL Server
- 4:28Isolation levels
- 10:50Read committed isolation
- 11:33Repeatable read and phantoms
- 16:13Serializable isolation
- 24:06Isolation trade-offs
- 25:27Deadlocks in SQL Server
- 33:18Deadlocks with merge
- 41:47Snapshot isolation
- 47:04Durability and transaction log mechanics
- 49:10Delayed durability
- 50:36Key takeaways
related talks
52mACID in SQL Server: what it is, how it works, and how to live more adventurously.
52mACID in SQL Server: what it is, how it works, and how to live more adventurously.
38mThe I in ACID
52mTransactions: Myths, Surprises and Opportunities
41mThe I in ACID
47mMaximizing Database Performance With Isolation Levels
01mDon't Drop ACID - Transactions in Distributed NoSQL
58mDon’t Drop ACID - Transactions in Distributed NoSQL
