Optimized Locking in SQL Server 2025: Internals, Contention, and Concurrency
Regular 50 minute session for SQLBits 2026Thursday - 23 Apr 2026 - 11:20 - 12:10 Room 2BTL; DR
Explore SQL Server 2025 locking internals, including Optimized Locking and Lock After Qualification. Learn how these changes reduce contention, blocking, and deadlocks, and how to analyze and optimize concurrency using DMVs and Extended Events.
Session Details
Optimized Locking in SQL Server 2025 introduces a fundamental redesign of how the storage engine synchronizes concurrent data modifications. By shifting long-lived protection from row and page resources to transaction-level ownership, the engine significantly reduces lock memory consumption, blocking chains, and deadlock susceptibility in high-throughput OLTP workloads.
A central innovation is the Lock After Qualification (LAQ) execution model. Instead of acquiring update locks during the scan phase, SQL Server evaluates row qualification optimistically using versioned visibility semantics and synchronizes only when correctness requires it. Through internal predicate-outcome heuristics, the engine can bypass certain conflicting rows without waiting while still preserving full ACID guarantees.
In this session, we will analyze the redesigned locking pipeline step-by-step:
• TID Locks – how transaction ownership replaces many traditional row locks
• LAQ mechanics – separating qualification from physical modification
• Conflict resolution patterns – why some write-write conflicts no longer cause blocking
• Correctness safeguards – commit-dependent predicate reasoning and re-qualification
Using targeted demos with sys.dm_tran_locks, sys.dm_os_waiting_tasks, execution plan analysis, and page-level inspection techniques, we correlate observable lock behavior with the underlying storage engine state. By examining page headers and row structures, we visualize transaction ownership, version pointers, and in-row versus off-row version storage in the Persistent Version Store (PVS).
We conclude by exploring practical workload implications, including index access paths, hotspot patterns, and scenarios where the engine must fall back to classic locking semantics.
Attendees will leave with a precise mental model of SQL Server 2025’s evolved locking pipeline - and actionable guidance for designing workloads that benefit from reduced contention, improved scalability, and more predictable concurrency behavior.
A central innovation is the Lock After Qualification (LAQ) execution model. Instead of acquiring update locks during the scan phase, SQL Server evaluates row qualification optimistically using versioned visibility semantics and synchronizes only when correctness requires it. Through internal predicate-outcome heuristics, the engine can bypass certain conflicting rows without waiting while still preserving full ACID guarantees.
In this session, we will analyze the redesigned locking pipeline step-by-step:
• TID Locks – how transaction ownership replaces many traditional row locks
• LAQ mechanics – separating qualification from physical modification
• Conflict resolution patterns – why some write-write conflicts no longer cause blocking
• Correctness safeguards – commit-dependent predicate reasoning and re-qualification
Using targeted demos with sys.dm_tran_locks, sys.dm_os_waiting_tasks, execution plan analysis, and page-level inspection techniques, we correlate observable lock behavior with the underlying storage engine state. By examining page headers and row structures, we visualize transaction ownership, version pointers, and in-row versus off-row version storage in the Persistent Version Store (PVS).
We conclude by exploring practical workload implications, including index access paths, hotspot patterns, and scenarios where the engine must fall back to classic locking semantics.
Attendees will leave with a precise mental model of SQL Server 2025’s evolved locking pipeline - and actionable guidance for designing workloads that benefit from reduced contention, improved scalability, and more predictable concurrency behavior.
3 things you'll get out of this session
* Understand how SQL Server 2025’s optimized locking engine changes lock acquisition and concurrency behavior
* Learn how to analyze blocking, lock escalation, and contention scenarios using DMVs and Extended Events
* Apply practical strategies in query design, indexing, and transactions to maximize concurrency and stability
* Learn how to analyze blocking, lock escalation, and contention scenarios using DMVs and Extended Events
* Apply practical strategies in query design, indexing, and transactions to maximize concurrency and stability
Speakers
Torsten Strauß's other proposed sessions for 2026
Analyzing Azure SQL Database Workloads with KQL Insights, Patterns, and Performance - 2026
Bicep on Azure – Building Modular and Reusable Infrastructure as Code - 2026
Deep Dive into Memory Grants:Diagnosing and Optimizing Query Performance in Azure SQL and SQL Server - 2026
End-to-End Database DevOps: Building Automated CI/CD Pipelines for Azure SQL - 2026
Hybrid Data in Motion: Near Real-Time Mirroring from SQL Server 2025 into Microsoft Fabric - 2026
Inside Data Compression in SQL Server and Azure SQL: Performance Gains, Trade-offs, and Engine Inter - 2026
Performance Unleashed: Practical Tuning for Azure SQL and SQL Server - 2026
Plan Cache Internals in SQL : Parameter Sensitive Plans, Cache Optimization, and Monitoring - 2026
Streamlined Deployments: Robust YAML CI/CD Pipelines for Azure Data Factory - 2026