FIX: Many xml_deadlock_report events are reported for one single intra-query deadlock occurrence in SQL Server 2016 and 2017

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


Assume that you use Microsoft SQL Server 2016 and 2017. If you enable the event xml_deadlock_report to collect data for deadlocks, many xml_deadlock_report events are reported for one single intra-query deadlock occurrence.


As a workaround for this issue, you can collect the error_reported XEvent by using a filter error_number = 1205 instead of xml_deadlock_report, as seen in the following example:


This issue is fixed in the following cumulative updates for SQL Server:

       Cumulative Update 10 for SQL Server 2017

       Cumulative Update 2 for SQL Server 2016 SP2

Note: With this fix, no xml_deadlock_report events are reported for intra-query deadlock when the deadlock can be resolved without killing a thread.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology that Microsoft uses to describe software updates.