Tomaž Kaštrun • 12/18/2025

Advent of 2025, Day 18 – SQL Server 2025 – Optimized locking

Read Original

This technical article details the 'Optimized Locking' feature in Microsoft SQL Server 2025. It explains how the feature, composed of Transaction ID (TID) locking and Lock After Qualification (LAQ), reduces lock memory usage, prevents lock escalation, and improves workload concurrency by releasing row locks sooner. The post includes a code example to check and enable the feature, which is disabled by default.

0 comments
#optimization #database #concurrency

Advent of 2025, Day 18 – SQL Server 2025 – Optimized locking

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
The Beautiful Web
Jens Oliver Meiert • 2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes
4
Wagon’s algorithm in Python
John D. Cook • 1 votes
5
An example conversation with Claude Code
Dumm Zeuch • 1 votes