Lock and Connection Management

Technical Article

The Lock Escalation Threshold – Part 1

  • Article

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.

You rated this post out of 5. Change rating

2022-09-19

External Article

Using Indexes to Bypass Locks

  • Article

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

Technical Article

Who's Blocking

  • Script

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 […]

(3)

You rated this post out of 5. Change rating

2007-04-19 (first published: )

7,480 reads

Technical Article

What's Running

  • Script

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.  […]

You rated this post out of 5. Change rating

2007-04-17 (first published: )

2,771 reads

Technical Article

Script to output dbcc inputbuffer adding spid info

  • Script

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 […]

You rated this post out of 5. Change rating

2006-10-19 (first published: )

2,364 reads

Blogs

Keeping Redshift System Table History Past 7 Days with S3 Tables

By

Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...

Updating the Data API Builder

By

I was updating my session for the Data API Builder (DAB) recently, mostly to...

T-SQL Tuesday #202 Invitation: That One SQL Server Outage You’ll Never Forget

By

I am excited to host T-SQL Tuesday for the first time. I want to...

Read the latest Blogs

Forums

advice on ssrs version control

By stan

Hi we're a bit behind on versioning ssrs.  I think we have over 1600...

Practical Ways to Approach SQL Server Problems and Case Studies

By academicexpertt

Working with SQL Server can involve more than just writing queries. Understanding database design,...

Measuring Productivity

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Measuring Productivity

Visit the forum

Question of the Day

Tracking All the Queries

I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?

See possible answers