November 13, 2011 at 11:34 am
Got it. Thank you both.
.
November 14, 2011 at 12:58 am
Never mind. I found the setting to turn on deadlock graphs in sql profiler. Working perfectly now. If anyone else is having this problem, be sure to click the "show all events" on the trace properties dialog. It's under the locks category.
All Events... is it really required? Use 'TSQL_Locks' template instead.
TSQL_Locks
Captures all of the Transact-SQL statements that are submitted to SQL Server by clients along with exceptional lock events. Use to troubleshoot deadlocks, lock time-out, and lock escalation events.
It covers following Event Classes.
Blocked Process Report
SP:StmtCompleted
SP:StmtStarting
SQL:StmtCompleted
SQL:StmtStarting
Deadlock Graph (Use against SQL Server 2005 or SQL Server 2008 instance.)
Lock:Cancel
Lock:Deadlock
Lock:Deadlock Chain
Lock:Escalation
Lock:Timeout (Use against SQL Server 2000 instance.)
Lock:Timeout (timeout>0) (Use against SQL Server 2005 or SQL Server 2008 instances.)
November 14, 2011 at 2:16 am
Dev (11/14/2011)
Never mind. I found the setting to turn on deadlock graphs in sql profiler. Working perfectly now. If anyone else is having this problem, be sure to click the "show all events" on the trace properties dialog. It's under the locks category.
All Events... is it really required?
Clicking the 'all events' option displays all the events for selection. It doesn't select all of them.
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
November 14, 2011 at 7:04 am
http://blogs.msdn.com/bartd/archive/2006/09/09/Deadlock-Troubleshooting_2C00_-Part-1.aspx
Note there are 2 additional parts to this blog series.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply