On Transactions and Atomic Operations
Proposed session for SQLBits 2026TL; DR
Transactions are critical when multiple changes need to be made entirely or not at all, but it’s rare to see transactions used at all in most production code. In this introductory session, we'll look at what transactions are and how they're used
Session Details
If there’s one thing that we, as SQL developers, don’t do, it’s use enough transactions. Transactions are critical when multiple changes need to be made entirely or not at all, but even given that, it’s rare to see transactions used at all in most production code.
In this session, we’ll look at what transactions are and why we should use them. We’ll explore the effects transactions have on locking and the transaction log. We’ll investigate methods of handling errors and undoing data modifications, and we’ll see why nested transactions are a lie.
In this session, we’ll look at what transactions are and why we should use them. We’ll explore the effects transactions have on locking and the transaction log. We’ll investigate methods of handling errors and undoing data modifications, and we’ll see why nested transactions are a lie.
3 things you'll get out of this session
Understand how SQL Server implements transactions
Learn why nested and named transactions can cause all sorts of problems
Learn how to implement transactions and error handling together
Speakers
Gail Shaw's other proposed sessions for 2026
All about Indexes - Part 1 - 2026
All about Indexes - Part 2 - 2026
Identifying the worst performing queries in a DB, with Query Store - 2026
KQL for the SQL Professional - 2026
Parameter Sniffing vs Parameter Sensitive Plan Optimization - 2026
Transaction Log Internals, unplugged - 2026