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-09-02 11:03
Critical5
Action0
Watch0
Stable0
Open actions53
Runtime events6789
Telemetry gaps18
Growth0.0 GB
Operational impact 0 / 100 High exposure ยท evidence coverage 60%
Recovery readiness Backup chains, restore confidence and failed maintenance are folded into each server's actions.
0
Capacity protection Low disk, database growth and projected pressure are visible before they become write failures.
0
Service reliability Failed jobs, runtime events, deadlocks, blocking and long-running queries are treated as connected reliability evidence.
6842
Data confidence Telemetry gaps are counted as risk so empty panels are not mistaken for healthy systems.
18
Action Center Backup Readiness Data Quality
Critical

SERVER 1

TESTSRV_1.DBNEXIA.COM / Test / SQL Server / Last seen 2026-09-02 11:00
Health10
Pressure100
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, 10 deadlocks and 0 blocking events appeared; databases grew by 0.0 GB in the selected window.

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: 10 action signals. The likely outcome is operational impact or missed recovery objectives unless the first action is handled immediately.

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
10 Locks
0 Queries
0 Gaps
10 blocking
Concrete findings 7
Deadlocks database unknown

2026-09-02 10:00 - <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-09-02T10:00:08.877Z"><data name="xml_report"><type name="xml" package="package0"...

Deadlocks database unknown

2026-09-02 10:00 - <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-09-02T10:00:08.877Z"><data name="xml_report"><value><deadlock><victim-list><vict...

Growth tempdb

0.0 GB growth (Data ).

Largest DB dbNexia_db

0.9 GB current size.

Largest DB MAL_MAINT_DB_old

0.1 GB current size.

Resources CPU and memory

CPU 1.0%, memory free 54.9%, users 2, transactions 11.

TempDB Data and log

Data 8.9%, log 7.3%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-09-02 11:00, last failed -. 10 deadlocks / 0 blocking. 0.0 GB growth. CPU 1.0%, memory free 54.9%. TempDB data 8.9%, log 7.3%.

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 1.0% / 54.9%
TempDB data / log 8.9% / 7.3%
Growth now / 7d forecast 0.0 GB / 0.0 GB
Runtime / 24h forecast 0 / 0
Backups / disks / jobs 0 / 0 / 0
Blocking / long queries 10 / 0
Telemetry gaps 0
Largest database 0.9 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 1.39 GB
Last OK 2026-09-02 11:00
Last failed -
Data quality 100%
Source confidence 0 gaps
AuditLog Available

dbNexia_db.dbo.AuditLog

DbSizes Available

dbNexia_db.dbo.dbsizes

EventLog Available

dbNexia_db.dbo.EventLog

LiveRequests Available

VIEW SERVER STATE permission

MsdbAgent Available

msdb SQL Agent history

MsdbBackup Available

msdb.dbo.backupset

ServerMetrics Available

dbNexia_db.dbo.ServerMetrics

TempDb Available

VIEW SERVER STATE permission

VolumeStats Available

VIEW SERVER STATE permission

Runtime 0 events

No runtime event sample was loaded for this server.

No latest runtime message captured.

Meaning

SQL Agent marked the failing step in job 'No runtime event sample was loaded for this server.' as failed.

Recommended fix

Open the job-history report for job 'No runtime event sample was loaded for this server.', read the full message for the failing step, apply the message-specific fix, then use Test run job from the dashboard if you have Admin/Moderator rights.

Verify

The latest row for the same job/step should show Succeeded and no new related EventLog error should appear.

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
tempdb4.0 MB

Data growth inside the selected 24h window.

Meaning and fix

Meaning: This signal is abnormal, but the row text is not specific enough to name a single root cause with confidence.

Fix: Use the row values already shown here to filter the related report by the same server, database/job/login and the same time window.

Verify: The signal should stop repeating in the next collection window after the underlying job, permission, backup, or workload issue is fixed.

Queries and concurrency10 signals
Deadlock2026-09-02 10:00

database unknown; <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-09-02T10:00:08.877Z"><data name="xml_report"><type name="xml" package="package0"...

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-09-02 10:00

database unknown; <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-09-02T10:00:08.877Z"><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-09-02 10:00

master; <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-09-02T10:00:08.877Z"><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-09-02 03:00

master; <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-09-02T03:00:09.449Z"><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-09-02 03:00

database unknown; <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-09-02T03:00:09.449Z"><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
dbNexia_db0.9 GB

Current largest database inventory sample.

MAL_MAINT_DB_old0.1 GB

Current largest database inventory sample.

DOM_DreamBlossom_D66E0.1 GB

Current largest database inventory sample.

DOM_ThunderMoon_622B0.1 GB

Current largest database inventory sample.

DOM_ShadowWhisper_67B10.1 GB

Current largest database inventory sample.

DOM_ForestDream_BD6D0.1 GB

Current largest database inventory sample.

DOM_BlossomWhisper_FDD30.0 GB

Current largest database inventory sample.

DBAChaos0.0 GB

Current largest database inventory sample.

tempdb0.0 GB

Current largest database inventory sample.

JobsNo failures

No SQL Agent job failures detected in this window.