How do I monitor deadlocks with the SQL Server profiler?
The profiler from SQL Server 2005 allows you to save the deadlock graph as an XML file. As well as the information that is also in the SQL Server error log (see above), this graph contains a lot of details (that are important for the analysis) about the processes and resources that are involved (for example, the isolation level of the processes and the names of the tables that are involved). Note 32129 describes how to set up this type of monitoring in an SAP system. The section “Analyzing Deadlocks with SQL Server Profiler” in SQL Server Books Online ( ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/72d6718f-501b-4ea6-b344-c0e653f19561.htm ) describes in detail how to create such a profiler trace. In the category ‘Locks’, you should select the ‘Deadlock Graph’, ‘Deadlock Chain’ and ‘Deadlock’ events. If you select ‘Deadlock Graph’, an additional tab (‘Events Extraction Settings’) appears, on which you can choose to save the graph as an XML file. However, after you create the trace in
