Database Reference
In-Depth Information
Figure 21-5. The XML information that defines the deadlock graph
If you look through this, you can see some of the information on display in the deadlock graph, but you also see
a whole lot more. For example, part of this deadlock actually involves code that I did not write or execute as part of
the example. There's a trigger on the table called uPurchaseOrderDetail . You can also see the code I used to generate
the deadlock. All this information can help you identify exactly which pieces of code lead to the deadlock. You also
get information such as the sqlhandle , which you can then use in combination with DMOs to pull statements and
execution plans out of cache. Because the plan is created before the query is run, it will be available for you even for
the queries that were chosen as the deadlock victim.
It's worth taking some time to explore this XML in a little more detail. Table 21-1 shows some of the elements
from the extended event and the information it represents.
 
Search WWH ::




Custom Search