February 10, 2012 at 8:30 am
What actions need to be taken when u get notification from third party tool for deadlocks occurred on server xxx is critical.
A deadlock occurred on server XXX. Full details are available in the Client Tool.
The deadlock victim was spid YY with application name 'unknown' by user 'ZZZ' on host 'unknown'.
Last command issued:
Having details......
Thanks
February 10, 2012 at 8:44 am
Sounds like you're using the Idera SQL diagnostic manager 😉
Have you been able to view the Deadlock graph? I believe it's "Show Deadlock View" - you have two different processes competing for the same resrouce...do you have control over these processes?
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
February 10, 2012 at 12:22 pm
If you don't have access to the report that has all the information, then you must have a traceflag enabled on the server so that the deadlock goes to the error log. If you have neither of those, then there's nothing you can do. You can't troubleshoot a deadlock issue without knowledge of what the two processes that deadlocked are.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 10, 2012 at 12:45 pm
Switch traceflag 1222 on. That will result in a deadlock graph been written to the error log every time a deadlock occurs. Post the result of that graph here if you want help interpreting it.
DBCC TRACEON(1222,-1)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply