How to Detect Deadlocking in SQL Server - Part 3

This video shows you how to detect deadlocks (error 1205) in your SQL Server Database.

Jonathan Kehayias is currently employed as a Principal Consultant and Trainer for SQLskills, one of the best-known and most respected SQL Server training and consulting companies in the world. Jonathan is a SQL Server MVP and one of the few Microsoft Certified Masters for SQL Server 2008, outside of Microsoft. Jonathan frequently blogs about SQL Server, presents sessions at PASS Summit, SQLBits, S...

BillRoger on 2/21/2009

nice trick. I can definitely use this trick to resolve deadlock at work. I am look forward to see more troubleshooting videos. very good info. Thanks

Brent on 3/12/2009

This is the wrong video..it is the one from your reversing deadlock series.

UB on 8/17/2009

Good info

Tobin on 9/15/2009

good

Paul Niland on 1/14/2010

It seems like there is a video missing between 2 and 3

Mark Holahan on 1/15/2010

There's a continuity break between Part 2 and Part 3. Seems like Part 3 should be Part 4 and Part 3 should really be the discussion of how to use the trace flag.

Dan Doucet on 4/19/2010

Excellent series! I think a more in depth explanation of how/why accessing tables in the same order clears things up would make it more helpful. Overall, though, great series! Thanks, Dan

Cole Knight on 4/19/2010

The stored procedures never did complete prior to the video ending. They sure ran for a long time.

ajoy.kumar on 4/22/2010

excellent

Tim on 6/2/2010

very helpful series

Ravi Raj on 6/24/2010

good article

yeskay on 7/8/2010

how would someone know that insert table order needs to be reversed.dificult for a novice to grasp, expected some more explanation

David Bridge on 1/12/2011

The author doesn't explain the reason behind the fix or investigate any other areas where this issue may occur. In this case the author knew exactly where the error was because it was created for the demo but had this been a real life issue the cause would be less obvious. What sequence of possibilities would the DBA check to detect the error. Is the table order the only one?

5124CFD2E1 on 8/24/2011

This appears to be related to another series, "Reverse Deadlocking". The deadlocks in this series had a S and X not X and X. How to Detect Deadlocking in SQL Server - Part 2