Skip to main content

How to export a deadlock graph from SQL Diagnostic Manager : Idera Diagnostic Manager

Hi guys!

 Today's post is on exporting a deadlock graph with Idera Diagnostic Manager.


 Idera Diagnostic Manager is a great tool to track performance issues in your SQL environment. 


 Let's get started.

 Open the application:
Idera SQL Diagnostic Manager startup




















Select the server:
Idera SQL Diagnostic Manager dashboard






Select the Sessions tab:
Idera SQL Diagnostic Manager Sessions









Select the Blocking option on the Sessions tab:
Idera SQL Diagnostic Manager Blocking












Select the History Browser :
Idera SQL Diagnostic Manager History Browser
Look for the culprit with a critical status of the Historical snapshots area in the bottom right:
a)
Idera SQL Diagnostic Manager History Browser











































b)
Idera SQL Diagnostic Manager History Browser
c)
Idera SQL Diagnostic Manager History Browser












































View session details for the culprit (session) that is causing all the issues:

 a)
Idera SQL Diagnostic Manager Session Details














































b) You can gather all the details to email to effected teams.
Idera SQL Diagnostic Manager Session Details














































Go back to the session blocking view:
Idera SQL Diagnostic Manager Session Details









Under Deadlock Reports, double click the most recent deadlock and 'Export XDL' (the deadlock graph) to your download folder on the server.
Idera SQL Diagnostic Manager Deadlock Graph XDL
b) Name your deadlock graph like this:
Idera SQL Diagnostic Manager Deadlock Graph XDL
c) Hit 'Done' to close out the deadlock window.
Idera SQL Diagnostic Manager Deadlock Graph XDL









































Locate your deadlock file and copy it to your desktop (ctrl c + ctrl v).
Idera SQL Diagnostic Manager Deadlock Graph XDL

Finally, email effected teams the deadlock information.
email deadlock graph details from Idera diagnostic manager











































If you have any questions related to this post, please put them below.


Thank you and Happy reading,

-marshé hutchinson
#learnSQLwithme
Labels:

Comments

Post a Comment

Popular posts from this blog

event id 101 task start failed - task scheduler event id 101 launch failure

Hello again. This post is related to automating SQL server tasks with Task Scheduler. In this example I was tasked with exporting SQL server agent jobs twice a month. To achieve this, I setup a task scheduler task that ran a PowerShell script that: establishes a local connection to the SQL server. cleans the file before writing to the .sql file to avoid adding on (appending) results on subsequent runs of the task scheduler task. when a connection is established, export the SQL agent jobs on the server to a .sql file on a remote server. sends a confirmation email via the SQL server database mail profile that the SQL agent jobs were exported to the specified remote server path. That was a mouthful. Now that you know my task scheduler task is calling a PowerShell script, let's get back to why it is failing.  The good news is this error is not related to the script. The error launch failure means the task could not even run. This is most likely due to a permissi
Post a Comment
Read more

Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 199 The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).

Hi guys! Here's another quick and easy post. Scenario I was trying to copy a SQL agent job from one server to another by just copying the script of that SQL job. You can copy any script by right clicking a job > Script job as > create to > new query window. I pasted the job on a different server and tried to execute it and received this error: Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 199 The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]). This error message is simply saying for the variable '@owner_login_name', the user account associated with the variable is incorrect because it does not exist. Fix Simply update the variable for '@owner_login_name' to a valid user account for the current SQL instance. Now when you execute the script again to create the SQL agent job your results will be: Command(s) completed successfully. If you have any furt
2 comments
Read more

Executed as user: . Incorrect syntax near ''. [SQLSTATE 42000] (Error 102). The step failed.

Hi everyone! Today's post is about an all too common problem... syntax issues. Whether you fat-finger your keyboard or are always in a rush, chances are you have already encountered many syntax errors. But if you are a newbie,  your syntax error is just around the corner. No worries, this is an easy fix. Syntax errors just let you know part of your code or script is incorrect. Scenario I have a SQL agent job that is using the SQL command line to perform index maintenance, but it is failing. Here's my code : sqlcmd -E -S $(ESCAPE_SQUOTE(SRVR)) -d master -Q "EXECUTE dbo.IndexOptimize @Databases = ' databaseName ', @FragmentationLow = NULL, @FragmentationMedium = 'INDEX_REORGANIZE,INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE', @FragmentationHigh = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE', @FragmentationLevel1 = 5, @FragmentationLevel2 = 30, @UpdateStatistics = 'ALL',@WaitAtLowPriorityMaxDuration = 180, @WaitAtLowPriorityAbortA
Post a Comment
Read more