Server Overview

Server operations cockpit

Pick a server and read the current story: what happened, what is happening, what happens next, and exactly what to do first.

Critical 2026-10-14 15:14
Critical3
Action3
Watch0
Stable0
Open actions30
Runtime events8319
Telemetry gaps0
Growth0.1 GB
Operational impact 0 / 100 High exposure ยท evidence coverage 83%
Recovery readiness Backup chains, restore confidence and failed maintenance are folded into each server's actions.
16
Capacity protection Low disk, database growth and projected pressure are visible before they become write failures.
10
Service reliability Failed jobs, runtime events, deadlocks, blocking and long-running queries are treated as connected reliability evidence.
8323
Data confidence Telemetry gaps are counted as risk so empty panels are not mistaken for healthy systems.
0
Action Center Backup Readiness Data Quality
Action

WIN-PN3T1M2LOOO

WIN-PN3T1M2LOOO / - / SQL Server / Last seen -
Health64
Pressure52
TrendDeteriorating
DirectionRising risk
Best advice

P1 Workload: Trace blockers/deadlocks to statement, index, and transaction order. This is first because concurrency incidents usually repeat under the same application path until the blocking pattern is removed. Pattern: Repeated blocking or deadlocks indicate a transaction, query, or indexing pattern.

Dashboard Report
What happened

In the selected window, 4 deadlocks and 0 blocking events appeared.

What is happening

Right now, sessions are waiting on blockers or deadlock-prone paths.

What happens next

Blocking and deadlock pressure is likely to repeat under the same workload until the blocking pattern is removed. Pressure indicators: 4 action signals. The likely outcome is repeated noise and growing maintenance debt unless an owner closes the action.

Actions to break the trend 1
P1
Workload

Trace blockers/deadlocks to statement, index, and transaction order.

Concurrency incidents usually repeat under the same application path until the blocking pattern is removed.
Trend and signal mix Rising risk
0 Backups
0 Disk
0 Jobs
0 Logs
4 Locks
0 Queries
0 Gaps
4 blocking
Concrete findings 2
Deadlocks master

2026-10-14 11:55 - <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-10-14T11:55:23.505Z"><data name="xml_report"><value><deadlock><victim-list><vict...

Deadlocks master

2026-10-13 17:40 - <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-10-13T17:40:19.837Z"><data name="xml_report"><value><deadlock><victim-list><vict...

Metrics and evidence Signals

4 deadlocks / 0 blocking.

Recommended action Identify blockers, statements, and transaction order; prioritize indexing or code changes.
Pattern Repeated blocking or deadlocks indicate a transaction, query, or indexing pattern.
Forecast Blocking and deadlock pressure is likely to repeat under the same workload until the blocking pattern is removed.
Break the trend remove blocker/deadlock source.
CPU / memory free - / -
TempDB data / log - / -
Growth now / 7d forecast 0.0 GB / 0.0 GB
Runtime / 24h forecast 0 / 0
Backups / disks / jobs 0 / 0 / 0
Blocking / long queries 4 / 0
Telemetry gaps 0
Largest database 0.0 GB
Operating profile -
Type SQL Server
Environment -
Repository size -
Last OK -
Last failed -
Data quality 0%
Source confidence 0 gaps
Source health No source rows

No source-health rows were loaded for this server. Treat missing evidence as unknown, not healthy.

Runtime 0 events

No runtime event sample was loaded for this server.

No latest runtime message captured.

Meaning

SQL Server detected two sessions holding resources in conflicting order and chose one session as the deadlock victim.

Recommended fix

Identify blockers, statements, and transaction order; prioritize indexing or code changes.

Verify

After the change, the same database/object pair should stop producing deadlock events in the selected lookback window.

Backup risks0
BackupsNo risks

No backup risks detected for this server.

Storage0 low volumes
StorageNo low volumes

No low free-space volumes detected for this server.

Growth0.0 GB
GrowthNo rows

No database growth rows detected for this window.

Queries and concurrency4 signals
Deadlock2026-10-14 11:55

master; <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-10-14T11:55:23.505Z"><data name="xml_report"><value><deadlock><victim-list><vict...

Meaning and fix

Meaning: SQL Server detected two sessions holding resources in conflicting order and chose one session as the deadlock victim.

Fix: Use the deadlock event details to identify the two statements and objects. Add the missing supporting index or change the transaction order so both code paths touch objects in the same order.

Verify: After the change, the same database/object pair should stop producing deadlock events in the selected lookback window.

Deadlock2026-10-13 17:40

master; <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-10-13T17:40:19.837Z"><data name="xml_report"><value><deadlock><victim-list><vict...

Meaning and fix

Meaning: SQL Server detected two sessions holding resources in conflicting order and chose one session as the deadlock victim.

Fix: Use the deadlock event details to identify the two statements and objects. Add the missing supporting index or change the transaction order so both code paths touch objects in the same order.

Verify: After the change, the same database/object pair should stop producing deadlock events in the selected lookback window.

Deadlock2026-10-13 15:55

master; <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-10-13T15:55:04.049Z"><data name="xml_report"><value><deadlock><victim-list><vict...

Meaning and fix

Meaning: SQL Server detected two sessions holding resources in conflicting order and chose one session as the deadlock victim.

Fix: Use the deadlock event details to identify the two statements and objects. Add the missing supporting index or change the transaction order so both code paths touch objects in the same order.

Verify: After the change, the same database/object pair should stop producing deadlock events in the selected lookback window.

Deadlock2026-10-13 15:35

master; <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-10-13T15:35:17.311Z"><data name="xml_report"><value><deadlock><victim-list><vict...

Meaning and fix

Meaning: SQL Server detected two sessions holding resources in conflicting order and chose one session as the deadlock victim.

Fix: Use the deadlock event details to identify the two statements and objects. Add the missing supporting index or change the transaction order so both code paths touch objects in the same order.

Verify: After the change, the same database/object pair should stop producing deadlock events in the selected lookback window.

Largest databases and job failures0 job failures
Largest databasesNo rows

No largest-database inventory rows detected.

JobsNo failures

No SQL Agent job failures detected in this window.