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 14:19
Critical3
Action3
Watch0
Stable0
Open actions29
Runtime events8219
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.
9
Service reliability Failed jobs, runtime events, deadlocks, blocking and long-running queries are treated as connected reliability evidence.
8223
Data confidence Telemetry gaps are counted as risk so empty panels are not mistaken for healthy systems.
0
Action Center Backup Readiness Data Quality
Critical

SERVER 2

TESTSRV_2.DBNEXIA.COM / Test / SQL Server / Last seen 2026-10-14 14:19
Health0
Pressure100
TrendDeteriorating
DirectionRising risk
Best advice

P1 Backup: Repair backup chain for DOM_DreamStone_5722 and validate restore. This is first because current evidence indicates high restore risk; this must be fixed before a real incident. Pattern: Multiple databases have backup chains without fresh evidence.

Dashboard Report
What happened

In the selected window, 7 database backup chains crossed the configured risk threshold; 2 volumes dropped below free-space policy; 2666 log/runtime events were recorded, latest at 2026-10-14 12:58; databases grew by 0.0 GB in the selected window.

What is happening

Right now, the error/log stream is active; storage headroom is below policy; restore confidence is degraded.

What happens next

Restore risk will continue to increase until the broken backup chain is repaired and verified. Pressure indicators: 2,666 projected runtime events in 24 hours, 9 action signals, 1 watch signals. The likely outcome is operational impact or missed recovery objectives unless the first action is handled immediately.

Actions to break the trend 3
P1
Backup

Repair backup chain for DOM_DreamStone_5722 and validate restore.

Current evidence indicates high restore risk; this must be fixed before a real incident.
P2
Storage

Plan capacity cleanup or extension for volumes below policy.

The trend is not yet critical, but continued growth will reduce the time available for a controlled fix.
P1
Logs

Group latest log errors by message and correlate with jobs, releases, and login sources.

The page sees a repeated symptom; grouping tells whether this is one noisy source or a wider server problem.
Trend and signal mix Rising risk
7 Backups
2 Disk
0 Jobs
2666 Logs
0 Locks
0 Queries
0 Gaps
7 backup 2 disk 2666 log/runtime
Concrete findings 12
Backups DOM_DreamStone_5722

FULL 17d ago, LOG 400h ago

Backups DOM_ForestEcho_B4A4

FULL 17d ago, LOG 400h ago

Backups DOM_ForestSky_5A7D

FULL 17d ago, LOG 400h ago

Disk ANNAT 1

13.4 GB free (33.4%) of 40.0 GB.

Disk ANNAT 1

13.4 GB free (33.4%) of 40.0 GB.

Logs 2,623 Errors

2026-10-14 12:58 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Logs 43 Timeouts

2026-10-14 12:58 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Growth dbNexia_db

0.0 GB growth (Log ).

Largest DB DOM_WhisperEcho_929E

0.5 GB current size.

Largest DB DOM_ShadowRiver_9AF6

0.4 GB current size.

Resources CPU and memory

CPU 17.0%, memory free 35.8%, users 2, transactions 8.

TempDB Data and log

Data 2.5%, log 8.8%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-10-14 14:19, last failed -. 7 backup risks. Worst disk ANNAT 1 13.4 GB (33.4%). 2666 runtime events. 0.0 GB growth.

Recommended action Repair the backup chain now and validate restore coverage for the highest-risk databases.
Pattern Multiple databases have backup chains without fresh evidence.
Forecast Restore risk will continue to increase until the broken backup chain is repaired and verified.
Break the trend validate backup and restore path; recover or extend disk capacity; triage latest log errors.
CPU / memory free 17.0% / 35.8%
TempDB data / log 2.5% / 8.8%
Growth now / 7d forecast 0.0 GB / 0.1 GB
Runtime / 24h forecast 2666 / 2666
Backups / disks / jobs 7 / 2 / 0
Blocking / long queries 0 / 0
Telemetry gaps 0
Largest database 0.5 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 3.58 GB
Last OK 2026-10-14 14:19
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 2666 events

Errors 2,623, timeouts 43, login failures 0, CPU warnings 0, memory grants 0.

(@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Meaning

database 'Errors 2,623, timeouts 43, login failures 0, CPU warnings 0, memory grants 0.' needs a newer log backup in the SQL backup chain.

Recommended fix

Run or repair the log-backup job for database 'Errors 2,623, timeouts 43, login failures 0, CPU warnings 0, memory grants 0.'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Backup risks7
DOM_DreamStone_5722808/100

FULL 17d ago, LOG 400h ago

Meaning and fix

Meaning: database 'DOM_DreamStone_5722' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_DreamStone_5722'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DOM_ForestEcho_B4A4808/100

FULL 17d ago, LOG 400h ago

Meaning and fix

Meaning: database 'DOM_ForestEcho_B4A4' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_ForestEcho_B4A4'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DOM_ForestSky_5A7D808/100

FULL 17d ago, LOG 400h ago

Meaning and fix

Meaning: database 'DOM_ForestSky_5A7D' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_ForestSky_5A7D'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DOM_ShadowRiver_9AF6808/100

FULL 17d ago, LOG 400h ago

Meaning and fix

Meaning: database 'DOM_ShadowRiver_9AF6' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_ShadowRiver_9AF6'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DOM_WhisperEcho_929E808/100

FULL 17d ago, LOG 400h ago

Meaning and fix

Meaning: database 'DOM_WhisperEcho_929E' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_WhisperEcho_929E'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DBAChaos408/100

FULL 17d ago

Meaning and fix

Meaning: database 'DBAChaos' is outside backup freshness policy.

Fix: Run or repair the full-backup job for database 'DBAChaos'. Verify target path, SQL Server service-account permissions, retention cleanup and free space before rerun.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

dbNexia_db408/100

FULL 17d ago

Meaning and fix

Meaning: database 'dbNexia_db' is outside backup freshness policy.

Fix: Run or repair the full-backup job for database 'dbNexia_db'. Verify target path, SQL Server service-account permissions, retention cleanup and free space before rerun.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Storage2 low volumes
ANNAT 113.4 GB free

33.4% free of 40.0 GB on T:\.

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.

ANNAT 113.4 GB free

33.4% free of 40.0 GB on T:\.

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.

Growth0.0 GB
dbNexia_db16.0 MB

Log 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 concurrency0 signals
Queries and concurrencyNo signals

No long running, blocking, or deadlock signals detected in this window.

Largest databases and job failures0 job failures
DOM_WhisperEcho_929E0.5 GB

Current largest database inventory sample.

DOM_ShadowRiver_9AF60.4 GB

Current largest database inventory sample.

DOM_ForestSky_5A7D0.4 GB

Current largest database inventory sample.

DOM_ForestEcho_B4A40.4 GB

Current largest database inventory sample.

DOM_DreamStone_57220.4 GB

Current largest database inventory sample.

dbNexia_db0.1 GB

Current largest database inventory sample.

DBAChaos0.1 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.

Critical

SERVER 3

TESTSRV_3.DBNEXIA.COM / Test / SQL Server / Last seen 2026-10-14 14:19
Health0
Pressure100
TrendDeteriorating
DirectionRising risk
Best advice

P1 Backup: Repair backup chain for DOM_CrystalStone_911A and validate restore. This is first because current evidence indicates high restore risk; this must be fixed before a real incident. Pattern: Multiple databases have backup chains without fresh evidence.

Dashboard Report
What happened

In the selected window, 7 database backup chains crossed the configured risk threshold; 2 volumes dropped below free-space policy; 2648 log/runtime events were recorded, latest at 2026-10-14 12:58; databases grew by 0.0 GB in the selected window.

What is happening

Right now, the error/log stream is active; storage headroom is below policy; restore confidence is degraded.

What happens next

Restore risk will continue to increase until the broken backup chain is repaired and verified. Pressure indicators: 2,648 projected runtime events in 24 hours, 9 action signals, 1 watch signals. The likely outcome is operational impact or missed recovery objectives unless the first action is handled immediately.

Actions to break the trend 3
P1
Backup

Repair backup chain for DOM_CrystalStone_911A and validate restore.

Current evidence indicates high restore risk; this must be fixed before a real incident.
P2
Storage

Plan capacity cleanup or extension for volumes below policy.

The trend is not yet critical, but continued growth will reduce the time available for a controlled fix.
P1
Logs

Group latest log errors by message and correlate with jobs, releases, and login sources.

The page sees a repeated symptom; grouping tells whether this is one noisy source or a wider server problem.
Trend and signal mix Rising risk
7 Backups
2 Disk
0 Jobs
2648 Logs
0 Locks
0 Queries
0 Gaps
7 backup 2 disk 2648 log/runtime
Concrete findings 12
Backups DOM_CrystalStone_911A

FULL 17d ago, LOG 400h ago

Backups DOM_FlameCrystal_07F4

FULL 17d ago, LOG 400h ago

Backups DOM_MoonCrystal_16FD

FULL 17d ago, LOG 400h ago

Disk ANNAT 1

13.4 GB free (33.4%) of 40.0 GB.

Disk ANNAT 1

13.4 GB free (33.4%) of 40.0 GB.

Logs 2,612 Errors

2026-10-14 12:58 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Logs 36 Timeouts

2026-10-14 12:58 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Growth dbNexia_db

0.0 GB growth (Log ).

Largest DB DOM_ShadowOcean_4486

0.5 GB current size.

Largest DB DOM_ShadowMoon_946A

0.4 GB current size.

Resources CPU and memory

CPU 17.0%, memory free 35.8%, users 2, transactions 14.

TempDB Data and log

Data 2.1%, log 3.1%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-10-14 14:19, last failed -. 7 backup risks. Worst disk ANNAT 1 13.4 GB (33.4%). 2648 runtime events. 0.0 GB growth.

Recommended action Repair the backup chain now and validate restore coverage for the highest-risk databases.
Pattern Multiple databases have backup chains without fresh evidence.
Forecast Restore risk will continue to increase until the broken backup chain is repaired and verified.
Break the trend validate backup and restore path; recover or extend disk capacity; triage latest log errors.
CPU / memory free 17.0% / 35.8%
TempDB data / log 2.1% / 3.1%
Growth now / 7d forecast 0.0 GB / 0.1 GB
Runtime / 24h forecast 2648 / 2648
Backups / disks / jobs 7 / 2 / 0
Blocking / long queries 0 / 0
Telemetry gaps 0
Largest database 0.5 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 4.14 GB
Last OK 2026-10-14 14:19
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 2648 events

Errors 2,612, timeouts 36, login failures 0, CPU warnings 0, memory grants 0.

(@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Meaning

database 'Errors 2,612, timeouts 36, login failures 0, CPU warnings 0, memory grants 0.' needs a newer log backup in the SQL backup chain.

Recommended fix

Run or repair the log-backup job for database 'Errors 2,612, timeouts 36, login failures 0, CPU warnings 0, memory grants 0.'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Backup risks7
DOM_CrystalStone_911A808/100

FULL 17d ago, LOG 400h ago

Meaning and fix

Meaning: database 'DOM_CrystalStone_911A' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_CrystalStone_911A'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DOM_FlameCrystal_07F4808/100

FULL 17d ago, LOG 400h ago

Meaning and fix

Meaning: database 'DOM_FlameCrystal_07F4' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_FlameCrystal_07F4'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DOM_MoonCrystal_16FD808/100

FULL 17d ago, LOG 400h ago

Meaning and fix

Meaning: database 'DOM_MoonCrystal_16FD' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_MoonCrystal_16FD'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DOM_ShadowMoon_946A808/100

FULL 17d ago, LOG 400h ago

Meaning and fix

Meaning: database 'DOM_ShadowMoon_946A' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_ShadowMoon_946A'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DOM_ShadowOcean_4486808/100

FULL 17d ago, LOG 400h ago

Meaning and fix

Meaning: database 'DOM_ShadowOcean_4486' needs a newer log backup in the SQL backup chain.

Fix: Run or repair the log-backup job for database 'DOM_ShadowOcean_4486'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

DBAChaos408/100

FULL 17d ago

Meaning and fix

Meaning: database 'DBAChaos' is outside backup freshness policy.

Fix: Run or repair the full-backup job for database 'DBAChaos'. Verify target path, SQL Server service-account permissions, retention cleanup and free space before rerun.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

dbNexia_db408/100

FULL 17d ago

Meaning and fix

Meaning: database 'dbNexia_db' is outside backup freshness policy.

Fix: Run or repair the full-backup job for database 'dbNexia_db'. Verify target path, SQL Server service-account permissions, retention cleanup and free space before rerun.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Storage2 low volumes
ANNAT 113.4 GB free

33.4% free of 40.0 GB on T:\.

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.

ANNAT 113.4 GB free

33.4% free of 40.0 GB on T:\.

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.

Growth0.0 GB
dbNexia_db18.0 MB

Log 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 concurrency0 signals
Queries and concurrencyNo signals

No long running, blocking, or deadlock signals detected in this window.

Largest databases and job failures0 job failures
DOM_ShadowOcean_44860.5 GB

Current largest database inventory sample.

DOM_ShadowMoon_946A0.4 GB

Current largest database inventory sample.

DOM_FlameCrystal_07F40.4 GB

Current largest database inventory sample.

DOM_CrystalStone_911A0.4 GB

Current largest database inventory sample.

DOM_MoonCrystal_16FD0.4 GB

Current largest database inventory sample.

tempdb0.1 GB

Current largest database inventory sample.

dbNexia_db0.1 GB

Current largest database inventory sample.

DBAChaos0.0 GB

Current largest database inventory sample.

JobsNo failures

No SQL Agent job failures detected in this window.

Critical

SERVER 5

TESTSRV_5.DBNEXIA.COM / Test / SQL Server / Last seen 2026-10-14 14:19
Health36
Pressure82
TrendDeteriorating
DirectionRising risk
Best advice

P1 Backup: Repair backup chain for DBAChaos and validate restore. This is first because current evidence indicates high restore risk; this must be fixed before a real incident. Pattern: Multiple databases have backup chains without fresh evidence.

Dashboard Report
What happened

In the selected window, 2 database backup chains crossed the configured risk threshold; 2 volumes dropped below free-space policy; 78 log/runtime events were recorded, latest at 2026-10-14 12:58; databases grew by 0.0 GB in the selected window.

What is happening

Right now, the error/log stream is active; storage headroom is below policy; restore confidence is degraded.

What happens next

Restore risk will continue to increase until the broken backup chain is repaired and verified. Pressure indicators: 78 projected runtime events in 24 hours, 4 action signals, 1 watch signals. The likely outcome is operational impact or missed recovery objectives unless the first action is handled immediately.

Actions to break the trend 3
P1
Backup

Repair backup chain for DBAChaos and validate restore.

Current evidence indicates high restore risk; this must be fixed before a real incident.
P2
Storage

Plan capacity cleanup or extension for volumes below policy.

The trend is not yet critical, but continued growth will reduce the time available for a controlled fix.
P1
Logs

Group latest log errors by message and correlate with jobs, releases, and login sources.

The page sees a repeated symptom; grouping tells whether this is one noisy source or a wider server problem.
Trend and signal mix Rising risk
2 Backups
2 Disk
0 Jobs
78 Logs
0 Locks
0 Queries
0 Gaps
2 backup 2 disk 78 log/runtime
Concrete findings 11
Backups DBAChaos

FULL 17d ago

Backups dbNexia_db

FULL 17d ago

Disk ANNAT 1

13.4 GB free (33.4%) of 40.0 GB.

Disk ANNAT 1

13.4 GB free (33.4%) of 40.0 GB.

Logs 39 Errors

2026-10-14 12:58 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Logs 39 Timeouts

2026-10-14 12:58 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Growth dbNexia_db

0.0 GB growth (Log ).

Largest DB DBAChaos

0.0 GB current size.

Largest DB dbNexia_db

0.0 GB current size.

Resources CPU and memory

CPU 17.0%, memory free 35.8%, users 2, transactions 11.

TempDB Data and log

Data 33.5%, log 10.8%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-10-14 14:19, last failed -. 2 backup risks. Worst disk ANNAT 1 13.4 GB (33.4%). 78 runtime events. 0.0 GB growth.

Recommended action Repair the backup chain now and validate restore coverage for the highest-risk databases.
Pattern Multiple databases have backup chains without fresh evidence.
Forecast Restore risk will continue to increase until the broken backup chain is repaired and verified.
Break the trend validate backup and restore path; recover or extend disk capacity; triage latest log errors.
CPU / memory free 17.0% / 35.8%
TempDB data / log 33.5% / 10.8%
Growth now / 7d forecast 0.0 GB / 0.1 GB
Runtime / 24h forecast 78 / 78
Backups / disks / jobs 2 / 2 / 0
Blocking / long queries 0 / 0
Telemetry gaps 0
Largest database 0.0 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 1.89 GB
Last OK 2026-10-14 14:19
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 78 events

Errors 39, timeouts 39, login failures 0, CPU warnings 0, memory grants 0.

(@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Meaning

database 'Errors 39, timeouts 39, login failures 0, CPU warnings 0, memory grants 0.' needs a newer log backup in the SQL backup chain.

Recommended fix

Run or repair the log-backup job for database 'Errors 39, timeouts 39, login failures 0, CPU warnings 0, memory grants 0.'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Backup risks2
DBAChaos408/100

FULL 17d ago

Meaning and fix

Meaning: database 'DBAChaos' is outside backup freshness policy.

Fix: Run or repair the full-backup job for database 'DBAChaos'. Verify target path, SQL Server service-account permissions, retention cleanup and free space before rerun.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

dbNexia_db408/100

FULL 17d ago

Meaning and fix

Meaning: database 'dbNexia_db' is outside backup freshness policy.

Fix: Run or repair the full-backup job for database 'dbNexia_db'. Verify target path, SQL Server service-account permissions, retention cleanup and free space before rerun.

Verify: Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Storage2 low volumes
ANNAT 113.4 GB free

33.4% free of 40.0 GB on T:\.

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.

ANNAT 113.4 GB free

33.4% free of 40.0 GB on T:\.

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.

Growth0.0 GB
dbNexia_db10.0 MB

Log 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 concurrency0 signals
Queries and concurrencyNo signals

No long running, blocking, or deadlock signals detected in this window.

Largest databases and job failures0 job failures
DBAChaos0.0 GB

Current largest database inventory sample.

dbNexia_db0.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.

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.

Action

SERVER 4

TESTSRV_4.DBNEXIA.COM / Test / SQL Server / Last seen 2026-10-14 14:19
Health64
Pressure46
TrendDeteriorating
DirectionRising risk
Best advice

P2 Storage: Plan capacity cleanup or extension for volumes below policy. This is first because the trend is not yet critical, but continued growth will reduce the time available for a controlled fix. Pattern: Errors, timeouts, login failures, CPU warnings, or memory grants are concentrated on this server.

Dashboard Report
What happened

In the selected window, 2 volumes dropped below free-space policy; 81 log/runtime events were recorded, latest at 2026-10-14 12:58; databases grew by 0.0 GB in the selected window.

What is happening

Right now, the error/log stream is active; storage headroom is below policy.

What happens next

The current log pace projects to about 81 runtime events over the next 24 hours. Pressure indicators: 81 projected runtime events in 24 hours, 2 action signals, 1 watch signals. The likely outcome is repeated noise and growing maintenance debt unless an owner closes the action.

Actions to break the trend 2
P2
Storage

Plan capacity cleanup or extension for volumes below policy.

The trend is not yet critical, but continued growth will reduce the time available for a controlled fix.
P1
Logs

Group latest log errors by message and correlate with jobs, releases, and login sources.

The page sees a repeated symptom; grouping tells whether this is one noisy source or a wider server problem.
Trend and signal mix Rising risk
0 Backups
2 Disk
0 Jobs
81 Logs
0 Locks
0 Queries
0 Gaps
2 disk 81 log/runtime
Concrete findings 9
Disk ANNAT 1

13.4 GB free (33.4%) of 40.0 GB.

Disk ANNAT 1

13.4 GB free (33.4%) of 40.0 GB.

Logs 41 Errors

2026-10-14 12:58 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Logs 40 Timeouts

2026-10-14 12:58 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Growth dbNexia_db

0.0 GB growth (Log ).

Largest DB dbNexia_db

0.1 GB current size.

Largest DB DBAChaos

0.0 GB current size.

Resources CPU and memory

CPU 17.0%, memory free 35.8%, users 2, transactions 8.

TempDB Data and log

Data 20.7%, log 20.4%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-10-14 14:19, last failed -. Worst disk ANNAT 1 13.4 GB (33.4%). 81 runtime events. 0.0 GB growth. CPU 17.0%, memory free 35.8%.

Recommended action Correlate the latest errors with jobs, application releases, and user traffic.
Pattern Errors, timeouts, login failures, CPU warnings, or memory grants are concentrated on this server.
Forecast The current log pace projects to about 81 runtime events over the next 24 hours.
Break the trend recover or extend disk capacity; triage latest log errors.
CPU / memory free 17.0% / 35.8%
TempDB data / log 20.7% / 20.4%
Growth now / 7d forecast 0.0 GB / 0.1 GB
Runtime / 24h forecast 81 / 81
Backups / disks / jobs 0 / 2 / 0
Blocking / long queries 0 / 0
Telemetry gaps 0
Largest database 0.1 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 1.95 GB
Last OK 2026-10-14 14:19
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 81 events

Errors 41, timeouts 40, login failures 0, CPU warnings 0, memory grants 0.

(@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Meaning

database 'Errors 41, timeouts 40, login failures 0, CPU warnings 0, memory grants 0.' needs a newer log backup in the SQL backup chain.

Recommended fix

Run or repair the log-backup job for database 'Errors 41, timeouts 40, login failures 0, CPU warnings 0, memory grants 0.'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Backup risks0
BackupsNo risks

No backup risks detected for this server.

Storage2 low volumes
ANNAT 113.4 GB free

33.4% free of 40.0 GB on T:\.

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.

ANNAT 113.4 GB free

33.4% free of 40.0 GB on T:\.

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.

Growth0.0 GB
dbNexia_db10.0 MB

Log 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 concurrency0 signals
Queries and concurrencyNo signals

No long running, blocking, or deadlock signals detected in this window.

Largest databases and job failures0 job failures
dbNexia_db0.1 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.

Action

SERVER 1

TESTSRV_1.DBNEXIA.COM / Test / SQL Server / Last seen 2026-10-14 14:19
Health73
Pressure33
TrendDeteriorating
DirectionRising risk
Best advice

P2 Storage: Plan capacity cleanup or extension for volumes below policy. This is first because the trend is not yet critical, but continued growth will reduce the time available for a controlled fix. Pattern: Errors, timeouts, login failures, CPU warnings, or memory grants are concentrated on this server.

Dashboard Report
What happened

In the selected window, 1 volumes dropped below free-space policy; 2746 log/runtime events were recorded, latest at 2026-10-14 12:58; databases grew by 0.0 GB in the selected window.

What is happening

Right now, the error/log stream is active; storage headroom is below policy.

What happens next

The current log pace projects to about 2,746 runtime events over the next 24 hours. Pressure indicators: 2,746 projected runtime events in 24 hours, 1 action signals, 1 watch signals. The likely outcome is repeated noise and growing maintenance debt unless an owner closes the action.

Actions to break the trend 2
P2
Storage

Plan capacity cleanup or extension for volumes below policy.

The trend is not yet critical, but continued growth will reduce the time available for a controlled fix.
P1
Logs

Group latest log errors by message and correlate with jobs, releases, and login sources.

The page sees a repeated symptom; grouping tells whether this is one noisy source or a wider server problem.
Trend and signal mix Rising risk
0 Backups
1 Disk
0 Jobs
2746 Logs
0 Locks
0 Queries
0 Gaps
1 disk 2746 log/runtime
Concrete findings 10
Disk ANNAT 1

13.4 GB free (33.4%) of 40.0 GB.

Logs 2,704 Errors

2026-10-14 12:58 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Logs 40 Timeouts

2026-10-14 12:58 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Logs 1 Login failures

2026-10-14 12:58 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Logs 1 Memory grants

2026-10-14 12:58 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Growth tempdb

0.0 GB growth (Log ).

Largest DB DOM_BlossomWhisper_FDD3

0.1 GB current size.

Largest DB DOM_ThunderMoon_622B

0.1 GB current size.

Resources CPU and memory

CPU 18.0%, memory free 35.8%, users 1, transactions 7.

TempDB Data and log

Data 3.6%, log 4.8%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-10-14 14:19, last failed -. Worst disk ANNAT 1 13.4 GB (33.4%). 2746 runtime events. 0.0 GB growth. CPU 18.0%, memory free 35.8%.

Recommended action Correlate the latest errors with jobs, application releases, and user traffic.
Pattern Errors, timeouts, login failures, CPU warnings, or memory grants are concentrated on this server.
Forecast The current log pace projects to about 2,746 runtime events over the next 24 hours.
Break the trend recover or extend disk capacity; triage latest log errors.
CPU / memory free 18.0% / 35.8%
TempDB data / log 3.6% / 4.8%
Growth now / 7d forecast 0.0 GB / 0.1 GB
Runtime / 24h forecast 2746 / 2746
Backups / disks / jobs 0 / 1 / 0
Blocking / long queries 0 / 0
Telemetry gaps 0
Largest database 0.1 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 3.58 GB
Last OK 2026-10-14 14:19
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 2746 events

Errors 2,704, timeouts 40, login failures 1, CPU warnings 0, memory grants 1.

(@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...

Meaning

database 'Errors 2,704, timeouts 40, login failures 1, CPU warnings 0, memory grants 1.' needs a newer log backup in the SQL backup chain.

Recommended fix

Run or repair the log-backup job for database 'Errors 2,704, timeouts 40, login failures 1, CPU warnings 0, memory grants 1.'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

Verify

Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.

Backup risks0
BackupsNo risks

No backup risks detected for this server.

Storage1 low volumes
ANNAT 113.4 GB free

33.4% free of 40.0 GB on T:\.

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.

Growth0.0 GB
tempdb20.0 MB

Log 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 concurrency0 signals
Queries and concurrencyNo signals

No long running, blocking, or deadlock signals detected in this window.

Largest databases and job failures0 job failures
DOM_BlossomWhisper_FDD30.1 GB

Current largest database inventory sample.

DOM_ThunderMoon_622B0.1 GB

Current largest database inventory sample.

DOM_DreamBlossom_D66E0.1 GB

Current largest database inventory sample.

DBAChaos0.1 GB

Current largest database inventory sample.

DOM_ShadowWhisper_67B10.1 GB

Current largest database inventory sample.

tempdb0.1 GB

Current largest database inventory sample.

JobsNo failures

No SQL Agent job failures detected in this window.