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.
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?
Hai buddies,The following procedure can be used to find whether there are any blocks in the sql server.The procedure if run in Master database , can be used like any other system stored procedure from any database.The output of the proc will contain the followingSPID OF RUNNING APPLICATIONAPPLICATION NAMEEXECUTING DATABLOCKED (Y/N)BLOCKING SPIDBLOCKING APPLICATIONEXECUTING DATA (BLOCKING […]
Please read the how to use. unfortunately the orignal document i submitted was truncated 🙁
and i dont have time to remember what i said
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 […]