SQL Server Deadlock Troubleshooting

Remember the previous customer in the use of software, there are occasional deadlock problems, because the time is uncertain, not good to reproduce the problem, at that time to solve the problem is a bit tricky.

Here is a summary of the two common ways to look at deadlocks:

The first is the graphical monitoring of:

SQL Server Profiler--and tools--when you log on in the trace properties, select such as:

The deadlock pattern heard by the supervisor

The description here is roughly: There are two processes one process ID is 96 and the other ID is 348. The system automatically killed the process id:96, leaving the process id:348 transaction commit

SQL Server Deadlock Troubleshooting