Analyze the Deadlock using the default system_health (Deadlock)

Before December 2008, we used profilertrace or traceflag1222, 1204. introduced a new feature in section 2008: ExtendedEvents (Extended events), which can monitor Deadlock events and improve performance.

Before December 2008, we used profilertrace or traceflag1222, 1204. introduced a new feature in section 2008: ExtendedEvents (Extended events), which can monitor Deadlock events and improve performance.

SELECT xed. value ('@ timestamp', 'datetime') as Creation_Date, xed. query ('. ') AS Extend_Event FROM (select cast ([target_data] as xml) AS Target_Data FROM sys. dm_xe_session_targetsAS xt INNERJOIN sys. dm_xe_sessions AS xs ONxs. address = xt. event_session_address WHERE xs. name = N 'System _ health' ANDxt.tar get_name = N 'ring _ buffer') AS XML_Data cross apply Target_Data.nodes ('ringbuffertarget/event [@ name = "xml_deadlock_report"] ') AS XEventData (xed) order by Creation_Date DESC

This article is from the "follow SQL Server Technology" blog. Be sure to keep this source

,