Skip to content

Commit 3e0c5aa

Browse files
BrentOzarclaude
andcommitted
Fix sp_BlitzLock qn column to restore 0-based numbering
The qn column was changed from ROW_NUMBER() - 1 (0-based) to ROW_NUMBER() (1-based), but downstream code still expects 0-based values. This caused parallel deadlocks to silently drop the second query (d.qn < 2 only keeps 1 row instead of 2) and made the WHEN d.qn = 0 labeling branch dead code. Fixes issue identified by Copilot in PR #3885. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 63470a8 commit 3e0c5aa

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

sp_BlitzLock.sql

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3618,7 +3618,7 @@ BEGIN
36183618
en =
36193619
DENSE_RANK() OVER (ORDER BY dp.event_date),
36203620
qn =
3621-
ROW_NUMBER() OVER (PARTITION BY dp.event_date ORDER BY dp.event_date),
3621+
ROW_NUMBER() OVER (PARTITION BY dp.event_date ORDER BY dp.event_date) - 1,
36223622
dn =
36233623
ROW_NUMBER() OVER (PARTITION BY dp.event_date, dp.id ORDER BY dp.event_date),
36243624
dp.is_victim,
@@ -3703,7 +3703,7 @@ BEGIN
37033703
en =
37043704
DENSE_RANK() OVER (ORDER BY dp.event_date),
37053705
qn =
3706-
ROW_NUMBER() OVER (PARTITION BY dp.event_date ORDER BY dp.event_date),
3706+
ROW_NUMBER() OVER (PARTITION BY dp.event_date ORDER BY dp.event_date) - 1,
37073707
dn =
37083708
ROW_NUMBER() OVER (PARTITION BY dp.event_date, dp.id ORDER BY dp.event_date),
37093709
is_victim = 1,

0 commit comments

Comments
 (0)