{"id":947,"date":"2009-02-23T13:49:00","date_gmt":"2009-02-23T13:49:00","guid":{"rendered":"\/blogs\/paul\/post\/Getting-historical-deadlock-info-using-extended-events.aspx"},"modified":"2017-04-13T09:51:49","modified_gmt":"2017-04-13T16:51:49","slug":"getting-historical-deadlock-info-using-extended-events","status":"publish","type":"post","link":"https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/","title":{"rendered":"Getting historical deadlock info using extended events"},"content":{"rendered":"

<\/p>\n

\nIn the TechNet Magazine article I wrote on Advanced Troubleshooting with Extended Events<\/a>, I mentioned the always-on event session called system_health. Jonathan Kehayias<\/a>, a fellow MVP and blogging mad-man, posted a great article<\/a> with SQL Server Central today about how to get historical deadlock graph info from it. His article explains some of the pre-reqs for doing this (like installing 2008 RTM CU1 – see KB 956717<\/a> – to get it working and a bug with the XML output) and gives some code.\n<\/p>\n

\nAfter wrestling with the download of CU1 (it took 5 tries to get it to download!), I got it installed in one of my VPCs and gave Jon's code a whirl. I forced a deadlock by creating two tables, locking them from separate transactions and then trying to select from the other table. See the code below:\n<\/p>\n

<\/p>\n

\n

\n\t— Connection 1:<\/font>
\n\tCREATE TABLE<\/font> t1 (<\/font>c1 INT<\/font>);<\/font>
\n\tINSERT INTO<\/font> t1 VALUES<\/font> (<\/font>1);<\/font>
\n\tGO\n\t<\/p>\n

\n\tBEGIN TRAN<\/font>
\n\tUPDATE<\/font> t1 SET<\/font> c1 =<\/font> 2;<\/font>
\n\tGO\n\t<\/p>\n

\n\t— Connection 2:<\/font>
\n\tCREATE TABLE<\/font> t2 (<\/font>c1 INT<\/font>);<\/font>
\n\tINSERT INTO<\/font> t2 VALUES<\/font> (<\/font>1);<\/font>
\n\tGO\n\t<\/p>\n

\n\tBEGIN TRAN<\/font>
\n\tUPDATE<\/font> t2 SET<\/font> c1 =<\/font> 2;<\/font>
\n\tGO\n\t<\/p>\n

\n\t— Connection 1:<\/font>
\n\tSELECT<\/font> *<\/font> FROM<\/font> t2;<\/font>
\n\tGO\n\t<\/p>\n

\n\t— Connection 2:<\/font>
\n\tSELECT<\/font> *<\/font> FROM<\/font> t1;<\/font>
\n\tGO\n\t<\/p>\n<\/blockquote>\n

<\/font><\/p>\n

\nAnd one of them will be killed by the deadlock monitor.\n<\/p>\n

<\/p>\n

\n

\n\tMsg 1205, Level 13, State 45, Line 1
\n\tTransaction (Process ID 57) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.<\/font>\n\t<\/p>\n<\/blockquote>\n

<\/font><\/p>\n

\nNow running Jon's (slightly reformatted) code:\n<\/p>\n

<\/p>\n

\n

\n\tSELECT <\/font>CAST <\/font>(<\/font>
\n\t    REPLACE <\/font>(<\/font>
\n\t        REPLACE <\/font>(<\/font>
\n\t            XEventData.<\/font>XEvent.<\/font>value (<\/font>'(data\/value)[1]'<\/font>,<\/font> 'varchar(max)'<\/font>),<\/font>
\n\t            '<victim-list>'<\/font>, <\/font>'<deadlock><victim-list>'<\/font>),<\/font>
\n\t        '<process-list>'<\/font>, <\/font>'<\/victim-list><process-list>'<\/font>)<\/font>
\n\t    AS XML<\/font>)<\/font> AS<\/font> DeadlockGraph
\n\tFROM <\/font>(<\/font>SELECT<\/font> CAST <\/font>(<\/font>target_data AS XML<\/font>)<\/font> AS<\/font> TargetData
\n\t    FROM<\/font> sys.dm_xe_session_targets<\/font> st
\n\t    JOIN<\/font> sys.dm_xe_sessions<\/font> s ON<\/font> s.<\/font>address =<\/font> st.<\/font>event_session_address
\n\t    WHERE<\/font> [name] = <\/font>'system_health'<\/font>)<\/font> AS<\/font> Data
\n\tCROSS APPLY<\/font> TargetData.<\/font>nodes (<\/font>'\/\/RingBufferTarget\/event'<\/font>)<\/font> AS<\/font> XEventData (<\/font>XEvent)<\/font>
\n\t    WHERE<\/font> XEventData.<\/font>XEvent.<\/font>value(<\/font>'@name'<\/font>, <\/font>'varchar(4000)'<\/font>) = <\/font>'xml_deadlock_report'<\/font>;<\/font>\n\t<\/p>\n<\/blockquote>\n

<\/font><\/p>\n

\nGives the XML deadlock graph (which unfortunately can't be displayed graphically because the format differs from the Profiler\/trace-flag output)\n<\/p>\n

<\/p>\n

\n\t<deadlock-list>
\n\t  <deadlock>
\n\t    <victim-list>
\n\t      <victimProcess id="process53d9000" \/>
\n\t    <\/victim-list>
\n\t    <process-list>
\n\t      <process id="process53d9000" taskpriority="0" logused="256" waitresource="RID: 1:1:304:0" waittime="331" ownerId="1868" transactionname="user_transaction" lasttranstarted="2009-02-23T13:32:05.100" XDES="0x4eb8c10" lockMode="S" schedulerid="1" kpid="2216" status="suspended" spid="57" sbid="0" ecid="0" priority="0" trancount="1" lastbatchstarted="2009-02-23T13:32:33.093" lastbatchcompleted="2009-02-23T13:32:05.100" clientapp="Microsoft SQL Server Management Studio – Query" hostname="CHICAGO" hostpid="2552" loginname="CHICAGO\\Administrator" isolationlevel="read committed (2)" xactid="1868" currentdb="1" lockTimeout="4294967295" clientoption1="671090784" clientoption2="390200">
\n\t        <executionStack>
\n\t          <frame procname="" line="1" sqlhandle="0x02000000c70b7b1daba27f2ddf3e772600949464d524b6f2" \/>
\n\t        <\/executionStack>
\n\t        <inputbuf>
\n\tSELECT * FROM t1;
\n\t    <\/inputbuf>
\n\t      <\/process>
\n\t      <process id="process4985558" taskpriority="0" logused="256" waitresource="RID: 1:1:294:0" waittime="10181" ownerId="1877" transactionname="user_transaction" lasttranstarted="2009-02-23T13:32:08.067" XDES="0x4eb9be0" lockMode="S" schedulerid="1" kpid="2020" status="suspended" spid="56" sbid="0" ecid="0" priority="0" trancount="1" lastbatchstarted="2009-02-23T13:32:23.240" lastbatchcompleted="2009-02-23T13:32:08.067" clientapp="Microsoft SQL Server Management Studio – Query" hostname="CHICAGO" hostpid="2552" loginname="CHICAGO\\Administrator" isolationlevel="read committed (2)" xactid="1877" currentdb="1" lockTimeout="4294967295" clientoption1="671090784" clientoption2="390200">
\n\t        <executionStack>
\n\t          <frame procname="" line="1" sqlhandle="0x02000000f4d34532698b7ad324df813feb2ba5024730cb79" \/>
\n\t        <\/executionStack>
\n\t        <inputbuf>
\n\tSELECT * FROM t2;
\n\t    <\/inputbuf>
\n\t      <\/process>
\n\t    <\/process-list>
\n\t    <resource-list>
\n\t      <ridlock fileid="1" pageid="304" dbid="1" objectname="" id="lock47aea80" mode="X" associatedObjectId="72057594039042048">
\n\t        <owner-list>
\n\t          <owner id="process4985558" mode="X" \/>
\n\t        <\/owner-list>
\n\t        <waiter-list>
\n\t          <waiter id="process53d9000" mode="S" requestType="wait" \/>
\n\t        <\/waiter-list>
\n\t      <\/ridlock>
\n\t      <ridlock fileid="1" pageid="294" dbid="1" objectname="" id="lock47af200" mode="X" associatedObjectId="72057594038976512">
\n\t        <owner-list>
\n\t          <owner id="process53d9000" mode="X" \/>
\n\t        <\/owner-list>
\n\t        <waiter-list>
\n\t          <waiter id="process4985558" mode="S" requestType="wait" \/>
\n\t        <\/waiter-list>
\n\t      <\/ridlock>
\n\t    <\/resource-list>
\n\t  <\/deadlock>
\n\t<\/deadlock-list>\n<\/p><\/blockquote>\n

<\/font><\/p>\n

\nCool!\n<\/p>\n

<\/font><\/p>\n","protected":false},"excerpt":{"rendered":"

In the TechNet Magazine article I wrote on Advanced Troubleshooting with Extended Events, I mentioned the always-on event session called system_health. Jonathan Kehayias, a fellow MVP and blogging mad-man, posted a great article with SQL Server Central today about how to get historical deadlock graph info from it. His article explains some of the pre-reqs […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[38,39,57,86],"tags":[],"class_list":["post-947","post","type-post","status-publish","format-standard","hentry","category-example-scripts","category-extended-events","category-locking","category-sql-server-2008"],"yoast_head":"\nGetting historical deadlock info using extended events - Paul S. Randal<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Getting historical deadlock info using extended events - Paul S. Randal\" \/>\n<meta property=\"og:description\" content=\"In the TechNet Magazine article I wrote on Advanced Troubleshooting with Extended Events, I mentioned the always-on event session called system_health. Jonathan Kehayias, a fellow MVP and blogging mad-man, posted a great article with SQL Server Central today about how to get historical deadlock graph info from it. His article explains some of the pre-reqs […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/\" \/>\n<meta property=\"og:site_name\" content=\"Paul S. Randal\" \/>\n<meta property=\"article:published_time\" content=\"2009-02-23T13:49:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2017-04-13T16:51:49+00:00\" \/>\n<meta name=\"author\" content=\"Paul Randal\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Paul Randal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/\",\"url\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/\",\"name\":\"Getting historical deadlock info using extended events - Paul S. Randal\",\"isPartOf\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/#website\"},\"datePublished\":\"2009-02-23T13:49:00+00:00\",\"dateModified\":\"2017-04-13T16:51:49+00:00\",\"author\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/#\/schema\/person\/ffcec826c18782e1e0adf173826a7fce\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Getting historical deadlock info using extended events\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/#website\",\"url\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/\",\"name\":\"Paul S. Randal\",\"description\":\"In Recovery...\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/#\/schema\/person\/ffcec826c18782e1e0adf173826a7fce\",\"name\":\"Paul Randal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/0b6a266bba2f088f2551ef529293001bd73bf026bc1908b9866728c062beeeb6?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/0b6a266bba2f088f2551ef529293001bd73bf026bc1908b9866728c062beeeb6?s=96&d=mm&r=g\",\"caption\":\"Paul Randal\"},\"sameAs\":[\"http:\/\/3.209.169.194\/blogs\/paul\"],\"url\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/author\/paul\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Getting historical deadlock info using extended events - Paul S. Randal","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/","og_locale":"en_US","og_type":"article","og_title":"Getting historical deadlock info using extended events - Paul S. Randal","og_description":"In the TechNet Magazine article I wrote on Advanced Troubleshooting with Extended Events, I mentioned the always-on event session called system_health. Jonathan Kehayias, a fellow MVP and blogging mad-man, posted a great article with SQL Server Central today about how to get historical deadlock graph info from it. His article explains some of the pre-reqs […]","og_url":"https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/","og_site_name":"Paul S. Randal","article_published_time":"2009-02-23T13:49:00+00:00","article_modified_time":"2017-04-13T16:51:49+00:00","author":"Paul Randal","twitter_misc":{"Written by":"Paul Randal","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/","url":"https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/","name":"Getting historical deadlock info using extended events - Paul S. Randal","isPartOf":{"@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/#website"},"datePublished":"2009-02-23T13:49:00+00:00","dateModified":"2017-04-13T16:51:49+00:00","author":{"@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/#\/schema\/person\/ffcec826c18782e1e0adf173826a7fce"},"breadcrumb":{"@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/getting-historical-deadlock-info-using-extended-events\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.sqlskills.com\/blogs\/paul\/"},{"@type":"ListItem","position":2,"name":"Getting historical deadlock info using extended events"}]},{"@type":"WebSite","@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/#website","url":"https:\/\/www.sqlskills.com\/blogs\/paul\/","name":"Paul S. Randal","description":"In Recovery...","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.sqlskills.com\/blogs\/paul\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/#\/schema\/person\/ffcec826c18782e1e0adf173826a7fce","name":"Paul Randal","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/0b6a266bba2f088f2551ef529293001bd73bf026bc1908b9866728c062beeeb6?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/0b6a266bba2f088f2551ef529293001bd73bf026bc1908b9866728c062beeeb6?s=96&d=mm&r=g","caption":"Paul Randal"},"sameAs":["http:\/\/3.209.169.194\/blogs\/paul"],"url":"https:\/\/www.sqlskills.com\/blogs\/paul\/author\/paul\/"}]}},"_links":{"self":[{"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/posts\/947","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/comments?post=947"}],"version-history":[{"count":0,"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/posts\/947\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/media?parent=947"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/categories?post=947"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/tags?post=947"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}