![]() SELECT CAST(C.query('.').value('(/event/data/value)', 'varchar(MAX)') AS XML) EventXMLĪND 'datetime') = ' 06:24:44.700' - Replace with relevant timestamp Parses the process list for a specific deadlock once provided with an event time for the deadlock from the above output Fetch the Health Session data into a temporary table Will provide you a parsed version of the process list in a tabular format whichĬan be easier to read when you have a large number of sessions involved in theĭeadlock. The next query (when provided with an event time from the above query output) ![]() WHERE 'varchar(255)') = 'xml_deadlock_report' Gets the Deadlock Event Time and Victim ProcessĬAST(C.query('.').value('(/event/data/value)', 'varchar(MAX)') AS VictimProcessĬROSS APPLY a.XMLDATA.nodes('/RingBufferTarget/event') as T(C) ON (xe.address = xet.event_session_address) SELECT CAST(xet.target_data AS XML) AS XMLDATA The query below will provide you with the time stamp when the deadlock was reported along with victim process identifier. Resource-list – Information about the resources involved in the deadlock Process-list – Information pertaining to all the processes involved in the deadlock Victim-list – Deadlock victim’s process identifier The deadlock graph captured typically has three distinct nodes: In this post, I shall show you how to extract deadlock related information from the deadlock graph captured by the System Health Session. ![]() This is the last post for the System Health Session series.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |