This article isn’t about the act of lock escalation itself, which is already well documented and generally well understood. Some myths (like row locks escalating to page locks) persist, but challenging those yet again probably wouldn’t change much.
2022-09-19
Reports summaries, in 3 levels of detail, connections, running requests, open transactions + cursors, and blocking. Provides query text + plan for the piggiest running request of each group.
2009-10-26 (first published: 2008-09-18)
6,032 reads
2008-05-16
3,650 reads
One of the issues you'll face with SQL Server is blocking which is caused by other processes that are holding locks on objects. Until the locks are removed on an object the next process will wait before proceeding. This is a common process that runs within SQL Server to ensure data integrity, but depending on how transactions are run this can cause some issues. Are there ways to get around blocking by using different indexes to cover the queries that may be running?
2008-05-02
3,383 reads
Script to log top blocker processes in a database. Top blocker is defined as the process that is at the top of a blocking chain.
2012-07-12 (first published: 2007-10-30)
3,019 reads
2007-10-19 (first published: 2007-07-25)
9,329 reads
A quick little standalone script that tells you what process is blocking and what processes the blocking processing actually blocking.When running this script in QA, change your output to "Results in Text" ( CTRL-T ). Utilizes the blocking info in sp_who2 combined with dbcc inputbuffer and a little cursor to wrap it all up. Formatting […]
2007-04-19 (first published: 2007-03-20)
7,467 reads
spWhatsRunning does just that. It tells you exactly what is executing on your server. By combining the output of the sp_who and dbcc inputbuffer, this script will tell you exactly whats being executed. DBCC INPUTBUFFER will tell you the same thing, but by the time you get the spid, the offending process may be gone. […]
2007-04-17 (first published: 2007-03-20)
2,761 reads
In this article I will try to justify why Table variables are superior to temporary tables.
2006-10-10
1,055 reads
The following script will allow the user to get information from all spids that have a program name associated with them. That is event info out of dbcc inputbuffer. Additional columns may be added and used in the table through simple modifications of the script. I just found it useful for troubleshooting and setting up […]
2006-10-19 (first published: 2006-09-29)
2,347 reads
By Brian Kelley
I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...
EightKB is back again for 2026! The biggest online SQL Server internals conference is...
By HeyMo0sh
Working in DevOps long enough teaches you two universal truths: That’s exactly why I...
Hi all, I just started using VS Code to work with DB projects. I...
Comments posted to this topic are about the item Fun with JSON II
Comments posted to this topic are about the item Changing Data Types
I have some data in a table:
CREATE TABLE #test_data
(
id INT PRIMARY KEY,
name VARCHAR(100),
birth_date DATE
);
-- Step 2: Insert rows
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT t1.[key] AS row,
t2.*
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t1
CROSS APPLY OPENJSON(t1.value) t2; See possible answers