Skip to content

Commit e2d85ed

Browse files
BrentOzarclaude
andcommitted
Fix XE event name in Azure help message: database_xml_deadlock_report
Azure SQL DB uses database_xml_deadlock_report, not xml_deadlock_report. Tested end-to-end: created the suggested XE session on Azure SQL DB, ran sp_BlitzLock successfully against it, and tore it back down. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 60b3141 commit e2d85ed

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

sp_BlitzLock.sql

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -580,7 +580,7 @@ To use sp_BlitzLock in Azure SQL DB, you have two options:
580580
1. Create a database-scoped deadlock XE session, e.g.:
581581
582582
CREATE EVENT SESSION [deadlocks] ON DATABASE
583-
ADD EVENT sqlserver.xml_deadlock_report
583+
ADD EVENT sqlserver.database_xml_deadlock_report
584584
ADD TARGET package0.ring_buffer;
585585
ALTER EVENT SESSION [deadlocks] ON DATABASE STATE = START;
586586

0 commit comments

Comments
 (0)