Optimized Locking in SQL Server 2025
Learn about Optimized Locking in the latest versions of SQL Server and Azure SQL Database.
2026-10-02
3,390 reads
Learn about Optimized Locking in the latest versions of SQL Server and Azure SQL Database.
2026-10-02
3,390 reads
Reproduce traditional row-lock accumulation and writer blocking, then see how SQL Server 2025 uses transaction ID locking and Lock After Qualification to improve concurrency—and where hints, isolation levels, and query shapes limit the benefit.
2026-09-23
3,154 reads
Learn about the impact of locking and blocking in sessions through some demonstrations of different types of actions.
2020-06-11
8,428 reads
By Steve Jones
I was experimenting with CHOOSE() recently after I was asked a question. In a...
By DesertDBA
I did not expect 27 responses to my T-SQL Tuesday #204 invitation, but it...
Should you adopt an off-the-shelf AI tool, partner with a specialist, build in-house, or...
Comments posted to this topic are about the item Switching Schema II
Comments posted to this topic are about the item A Practical Approach to Automating...
Comments posted to this topic are about the item Data Lost in the Cloud
I run this query:
SELECT s.name AS schemaname , o.name AS objectname FROM sys.objects o INNER JOIN sys.schemas s ON s.schema_id = o.schema_id WHERE o.name = 'Beer'I get two rows back for the objects, named dbo.beer and etl.beer. Both the tables have identical schemas and are not partitioned. There are 25 rows in dbo.beer and 0 rows in etl.beer. I run this code:
ALTER TABLE dbo.beer switch TO etl.beerWhat happens? See possible answers