Database Reference
In-Depth Information
When you capture the deadlock graph in SQL Profiler, you would see the graphics representation of the deadlock
chain, as shown in Figure 19-17 . As mentioned in the previous chapter, it is better to avoid using the client SQL
Profiler application in a production environment due to the overhead it introduces and use server-side traces instead.
You can open the trace file collected by the server side trace in the SQL Profiler application afterwards.
Figure 19-17. Deadlock Graph event in SQL Profiler
The graphic representation of the deadlock above shows the processes involved in the deadlock in the ovals and
the resources they are competing for in the rectangles. It also provides information about the lock types involved in
the deadlock with the arrows. You can see the statements involved in the deadlock by hovering over them with your
mouse pointer. Extract Event Data action from the event context menu allows you to extract a deadlock graph to an
XML-like file with many additional details.
XML representation of the deadlock graph contains two different sections, as shown in Listing 19-5.
Listing 19-5. Deadlock graph format
<deadlock-list>
<deadlock victim="...">
<process-list>
<process id="...">
...
</process>
<process id="...">
...
</process>
</process-list>
 
Search WWH ::




Custom Search