![]() ![]() You may also open the XDL file in an XML editor of your choice, if you would like to see the deadlock information in the XML format. The Management Studio (SSMS) is capable of opening the XDL files and representing the information as a deadlock graph.Īs you can see from the image above, hovering the mouse over the deadlock victim also reveals the affected query. To open these files, one does not need to use the SQL Profiler. Now that the deadlock information has been exported to the file system, you can now E-mail these files over to the development team who can in-turn analyze the deadlock graphs for you, and arrive at a resolution to the deadlock issue. Opening the trace in SQL Server Management Studio You may choose to save all events in a single file, or have separate files for each deadlock event. If you need to extract all deadlock graphs from a SQL Server profiler trace, go to File->Export->Extract SQL Server events->Extract Deadlock events…Įxport this information to a location of your choice in the form of SQL Server Deadlock XML files ( *.xdl). As the name indicates, it is ultimately an XML file containing the XML representation of the deadlock graph.Įxport Deadlock Data – Export all deadlock information The deadlock graph information is stored in the form of SQL Server Deadlock XML files ( *.xdl). Deadlock graph information can then be saved to any desired location of your choice. If only a selected deadlock needs to be forwarded to the development team for analysis, then, simply right-click on the deadlock and choose “Extract Event Data”. In case this deadlock needs to be sent over to the development team, one can follow one of the many steps highlighted belowĮxport Deadlock Data – Export Selected deadlock information only One can analyze the deadlock graph here itself. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |