Skip to main content

Capture the Deadlock-List from the Errorlog


What the script does
-------------------------
This script helps to identify the deadlock from the sql error log

Things to Note
-------------------
The script will only capture the deadlock in the most recent error log,
The first parameter in the "Sp_ReadErrorlog" needs to change in case the older deadlock are require.

Pre Requirements
------------------------
1204 or 1222 error flag needs to be enabled 



CREATE TABLE #Temp_All_LgData (ID int IDENTITY (1, 1), LogDate datetime, ProcessInfo nvarchar(50), LogText nvarchar(max))
CREATE TABLE #Temp_Results (ID int IDENTITY (1,1), LogDate datetime, ProcessInfo nvarchar(50), LogText nvarchar(max))
CREATE TABLE #Temp_DedLockID (ID int, processinfo nvarchar(50))

-- all the data in the error log will be recorded here
INSERT INTO #Temp_All_LgData
EXEC  sp_readerrorlog 0,1


--  only the records with "Deadlock-list" in the  text will be recorded
INSERT INTO #Temp_DedLockID
SELECT ID, processinfo
FROM #Temp_All_LgData
--WHERE LogText = 'deadlock-list' -- when trace flag 1222
WHERE LogText = 'Deadlock encountered .... Printing deadlock information' -- when trace flag 1204 is set

ORDER BY ID


DECLARE @StartID int, @ENDID int, @ProcessInfo nvarchar(50)
SELECT TOP 1 @StartID = ID FROM #Temp_DedLockID ORDER BY ID

WHILE(@@rowcount<>0)
BEGIN
    SELECT @ProcessInfo = ProcessInfo FROM #Temp_DedLockID WHERE ID = @StartID
    SELECT TOP 1 @ENDID = ID FROM #Temp_All_LgData WHERE ID > @StartID and ProcessInfo = @ProcessInfo ORDER BY ID DESC
   
    INSERT INTO #Temp_Results (LogDate, ProcessInfo, LogText)
    SELECT LogDate, ProcessInfo, LogText
    FROM #Temp_All_LgData
    WHERE
       ID >=@StartID and
       processinfo = @ProcessInfo and
       ID < @ENDID
    ORDER BY ID
   
    INSERT INTO #Temp_Results (LogDate, ProcessInfo, LogText)
    VALUES (GETDATE() , 'DEADLOCK   ' + @ProcessInfo  , 'END OF DEADLOCK   ' + @ProcessInfo ) ,(GETDATE() , 'NEW DEADLOCK' , '   NEXT DEADLOCK   ')
   
    DELETE #Temp_DedLockID WHERE ID = @StartID
    SELECT TOP 1 @StartID = ID FROM #Temp_DedLockID ORDER BY ID
      
   
   
END

SELECT LogDate, ProcessInfo, LogText
FROM #Temp_Results
ORDER BY ID



DROP TABLE #Temp_All_LgData
DROP TABLE #Temp_Results
DROP TABLE #Temp_DedLockID

Comments

Popular posts from this blog

High Watermarks For Incremental Models in dbt

The last few months it’s all been dbt. Dbt is a transform and load tool which is provided by fishtown analytics. For those that have created incremental models in dbt would have found the simplicity and easiness of how it drives the workload. Depending on the target datastore, the incremental model workload implementation changes. But all that said, the question is, should the incremental model use high-watermark as part of the implementation. How incremental models work behind the scenes is the best place to start this investigation. And when it’s not obvious, the next best place is to investigate the log after an test incremental model execution and find the implementation. Following are the internal steps followed for a datastore that does not support the merge statements. This was observed in the dbt log. - As the first step, It will copy all the data to a temp table generated from the incremental execution. - It will then delete all the data from the base table th

Create a dacpac To Compare Schema Differences

It's been some time since i added anything to the blog and a lot has happened in the last few months. I have run into many number of challenging stuff at Xero and spread my self to learn new things. As a start i want to share a situation where I used a dacpac to compare the differences of a database schema's. - This involves of creating the two dacpacs for the different databases - Comparing the two dacpacs and generating a report to know the exact differences - Generate a script that would have all the changes How to generate a dacbpac The easiest way to create a dacpac for a database is through management studio ( right click on the databae --> task --> Extract data-tier-application). This will work under most cases but will error out when the database has difffrent settings. ie. if CDC is enabled To work around this blocker, you need to use command line to send the extra parameters. Bellow is the command used to generate the dacpac. "%ProgramFiles

How To Execute A SQL Job Remotely

One of the clients needed its users to remotely execute a SQL job and as usual I picked this up hoping for a quick brownie point. Sure enough there was a catch and there was something to learn. Executing the job through SQLCMD was a no-brainer but getting it to execute on the remote machine was bit of challenge. On the coding Front 1    1.)     The bat file included the following code                 SQLCMD -S "[ServerName] " -E -Q "EXEC MSDB.dbo.sp_start_job @Job_Name = ' '[JobName]" 2    2.)     The Individual users were given minimum permissions  to execute the SQL job Ex. use msdb EXECUTE sp_addrolemember @rolename = 'SQLAgentOperatorRole', @membername = ' Domain\UserLogin ' At the client machine              This took a fair bit of time till our sysadmin got me an empty VM machine.  Thanks Michael G                   I’m just going to copy the exact instructions that I copied to OneNote and passed on