Blocking History - SQL01

Created: 2026-07-19 09:00:00
Source: www.powershelldba.de | sqmSQLTool v1.9.103.0
Illustrative example, this lab instance runs with the default "blocked process threshold (s)" server option of 0 (disabled), so the underlying Extended Events session captures nothing to report. Values below are representative, not measured output.

3 incident(s) in the retained Extended Events buffer (sqm_BlockedProcessMonitor session, last 24h).

TimeWaitDatabaseBlocked SPIDBlocking SPIDBlocked LoginBlocking LoginBlocked StatementBlocking Statement
2026-07-19 08:41:1272sSalesDB11287app_svcetl_svcUPDATE Orders SET Status = 'Shipped' WHERE OrderId = @idMERGE Orders AS tgt USING #StageOrders AS src ON tgt.OrderId = src.OrderId ...
2026-07-19 08:15:0314sSalesDB9487app_svcetl_svcSELECT * FROM Orders WITH (UPDLOCK) WHERE CustomerId = @cidMERGE Orders AS tgt USING #StageOrders AS src ON tgt.OrderId = src.OrderId ...
2026-07-19 07:58:414sReportingDB6358rpt_rorpt_etlSELECT SUM(Amount) FROM FactSales WHERE PeriodId = @pINSERT INTO FactSales SELECT * FROM #StageSales

Severity thresholds: >= 60s critical, >= 10s warning, below that informational. Head-blocker statement is truncated to 200 characters in the report.