Lock and Connection Management

Technical Article

The Ultimate Connection Summarizer and Trouble Finder

  • Script

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.

3.71 (7)

You rated this post out of 5. Change rating

2009-10-26 (first published: )

5,981 reads

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

2.33 (3)

You rated this post out of 5. Change rating

2007-04-19 (first published: )

7,440 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,712 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,308 reads

Blogs

A New Word: Vicarous

By

vicarous – adj. curious to know what someone else would do if they were...

SQL Server Cross Platform Availability Groups and Kubernetes

By

Say we have a database that we want to migrate a copy of into...

Using Managed Identities with Azure SQL DB

By

We are trying to get apps and users off of using SQL accounts to...

Read the latest Blogs

Forums

We Stink!

By Grant Fritchey

Comments posted to this topic are about the item We Stink!

View works for me ...but doesn't return results for a user in SSMS but no errors

By krypto69

Hi I have this view to check if a job is running:   SELECT...

Dark mode, other color schemes

By mjdemaris

All, if you are like me and do not care for the built-in color...

Visit the forum

Question of the Day

Internal Checkpoints

Certain internal SQL Server actions cause internal checkpoints. Which of these actions does not cause an internal checkpoint?

See possible answers