Optimized Locking: Improving SQL Server Transaction Concurrency ~ Deborah M.

Part 3 of a 4-part series about:
Hidden Pathways to Achieving Peak SQL Server Performance

Optimized Locking: Improving SQL Server Transaction Concurrency

Some aspects of the SQL Server engine have not seen much change for a long time - locking is one such component. Until now. Optimized locking is here and it affects not just the locking mechanisms but the way concurrency is handled. This session is designed to help us understand how optimized locking works. First we will cover the foundation on which it was built, the version store. Then we’ll dig deep into the two components of optimized locking: Transaction ID (TID) and lock after qualification (LAQ). Finally, we’ll review some best practices when enabled. By the end of this session, you should have a clear understanding of how it works and why we want to take advantage of this new functionality.

Session Goals: • Understand what a version store is and where it is persisted • Understand the two components of optimized locking: Transaction ID & Lock After Qualification (LAQ) • Understand some best practices surrounding optimized locking
Session Prerequisites: Basic understanding of different isolation levels and concurrency concepts