Blocking Analysis Export

Blocking Incident Report

Exported incident snapshot from the Blocking Analysis module. This file summarizes the captured blocker chain, the affected sessions, and the operational interpretation of the incident detected on June 1, 2026.

Generated At 2026-06-01 12:16:05
Chain Count 1
Affected Sessions 4
Max Chain Depth 3
Total Wait 171,529 ms
Chain Peak Wait 59,074 ms
Head Blocker

Primary Root Session

  • SPID 120
  • Database: WideWorldImporters
  • Login: adamsmith
  • Observed Wait: 59.1 seconds
Operator Reading

Interpretation

  • A single head blocker is responsible for the visible chain.
  • The chain reached depth 3, so contention propagated beyond one direct victim.
  • The longest blocked session crossed the one-minute threshold for urgent review.
  • Captured evidence should be reviewed before any kill action or rollback decision.
Blocking Sessions

Captured Session Evidence

Session Blocked By Wait Type Wait Severity Safe Kill
125 120 LCK_M_X 59,074 ms high yes
117 125 LCK_M_X 57,374 ms high yes
99 125 LCK_M_X 55,081 ms high yes
Lock Summary

High-Level Lock Footprint

The exported incident shows the blocker holding database and key-level locks in WideWorldImporters. The detailed raw lock list is preserved in the Markdown companion file for deeper forensic review.

Session Resource Type Mode Status Count
120 DATABASE S GRANT 1
120 KEY X GRANT multiple
Recommended Review Flow

Suggested Operator Sequence

  1. Confirm the head blocker in graph or tree view.
  2. Read the SQL text and session summary before intervention.
  3. Inspect lock granularity and downstream impact.
  4. Review recurrence history to distinguish one-off versus chronic blockers.
  5. Export evidence before killing a session in production.
This HTML file is a curated export companion. For the raw, full lock-detail dump captured by the module, download the Markdown report that was generated from the same incident snapshot.
Download Markdown Companion Open Module Documentation