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-17 11:03
Critical3
Action3
Watch0
Stable0
Open actions26
Runtime events8267
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.
8268
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-17 11:00
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; 2634 log/runtime events were recorded, latest at 2026-10-17 09:41; 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,634 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
2634 Logs
0 Locks
0 Queries
0 Gaps
7 backup 2 disk 2634 log/runtime
Concrete findings 12
Backups DOM_DreamStone_5722

FULL 20d ago, LOG 469h ago

Backups DOM_ForestEcho_B4A4

FULL 20d ago, LOG 469h ago

Backups DOM_ForestSky_5A7D

FULL 20d ago, LOG 469h ago

Disk ANNAT 1

11.7 GB free (29.2%) of 40.0 GB.

Disk ANNAT 1

11.7 GB free (29.2%) of 40.0 GB.

Logs 2,596 Errors

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

Logs 36 Timeouts

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

Logs 1 Login failures

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

Logs 1 Memory grants

2026-10-17 09:41 - (@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_WhisperEcho_929E

0.6 GB current size.

Largest DB DOM_ShadowRiver_9AF6

0.5 GB current size.

Metrics and evidence Signals

Last OK 2026-10-17 11:00, last failed -. 7 backup risks. Worst disk ANNAT 1 11.7 GB (29.2%). 2634 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 10.0% / 41.8%
TempDB data / log 1.3% / 2.5%
Growth now / 7d forecast 0.0 GB / 0.3 GB
Runtime / 24h forecast 2634 / 2634
Backups / disks / jobs 7 / 2 / 0
Blocking / long queries 0 / 0
Telemetry gaps 0
Largest database 0.6 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 3.58 GB
Last OK 2026-10-17 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 2634 events

Errors 2,596, timeouts 36, 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,596, timeouts 36, 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,596, timeouts 36, 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 risks7
DOM_DreamStone_5722949/100

FULL 20d ago, LOG 469h 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_B4A4949/100

FULL 20d ago, LOG 469h 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_5A7D949/100

FULL 20d ago, LOG 469h 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_9AF6949/100

FULL 20d ago, LOG 469h 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_929E949/100

FULL 20d ago, LOG 469h 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.

DBAChaos480/100

FULL 20d 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_db480/100

FULL 20d 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 111.7 GB free

29.2% 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 111.7 GB free

29.2% 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
tempdb37.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.6 GB

Current largest database inventory sample.

DOM_ShadowRiver_9AF60.5 GB

Current largest database inventory sample.

DOM_ForestSky_5A7D0.5 GB

Current largest database inventory sample.

DOM_ForestEcho_B4A40.5 GB

Current largest database inventory sample.

DOM_DreamStone_57220.5 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 3

TESTSRV_3.DBNEXIA.COM / Test / SQL Server / Last seen 2026-10-17 11:00
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; 2661 log/runtime events were recorded, latest at 2026-10-17 09:41; 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,661 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
2661 Logs
0 Locks
0 Queries
0 Gaps
7 backup 2 disk 2661 log/runtime
Concrete findings 12
Backups DOM_CrystalStone_911A

FULL 20d ago, LOG 469h ago

Backups DOM_FlameCrystal_07F4

FULL 20d ago, LOG 469h ago

Backups DOM_MoonCrystal_16FD

FULL 20d ago, LOG 469h ago

Disk ANNAT 1

11.7 GB free (29.2%) of 40.0 GB.

Disk ANNAT 1

11.7 GB free (29.2%) of 40.0 GB.

Logs 2,602 Errors

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

Logs 51 Timeouts

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

Logs 4 Login failures

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

Logs 4 Memory grants

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

Growth DOM_CrystalStone_911A

0.0 GB growth (Log ).

Largest DB DOM_ShadowOcean_4486

0.5 GB current size.

Largest DB DOM_ShadowMoon_946A

0.5 GB current size.

Metrics and evidence Signals

Last OK 2026-10-17 11:00, last failed -. 7 backup risks. Worst disk ANNAT 1 11.7 GB (29.2%). 2661 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 10.0% / 41.8%
TempDB data / log 1.9% / 6.9%
Growth now / 7d forecast 0.0 GB / 0.1 GB
Runtime / 24h forecast 2661 / 2661
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-17 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 2661 events

Errors 2,602, timeouts 51, login failures 4, CPU warnings 0, memory grants 4.

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

Meaning

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

Recommended fix

Run or repair the log-backup job for database 'Errors 2,602, timeouts 51, login failures 4, CPU warnings 0, memory grants 4.'. 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_911A949/100

FULL 20d ago, LOG 469h 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_07F4949/100

FULL 20d ago, LOG 469h 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_16FD949/100

FULL 20d ago, LOG 469h 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_946A949/100

FULL 20d ago, LOG 469h 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_4486949/100

FULL 20d ago, LOG 469h 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.

DBAChaos480/100

FULL 20d 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_db480/100

FULL 20d 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 111.7 GB free

29.2% 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 111.7 GB free

29.2% 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
DOM_CrystalStone_911A15.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.5 GB

Current largest database inventory sample.

DOM_FlameCrystal_07F40.5 GB

Current largest database inventory sample.

DOM_CrystalStone_911A0.5 GB

Current largest database inventory sample.

DOM_MoonCrystal_16FD0.5 GB

Current largest database inventory sample.

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

Critical

SERVER 5

TESTSRV_5.DBNEXIA.COM / Test / SQL Server / Last seen 2026-10-17 11:00
Health45
Pressure69
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; 1 volumes dropped below free-space policy; 123 log/runtime events were recorded, latest at 2026-10-17 09:41; 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: 123 projected runtime events in 24 hours, 3 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
1 Disk
0 Jobs
123 Logs
0 Locks
0 Queries
0 Gaps
2 backup 1 disk 123 log/runtime
Concrete findings 12
Backups DBAChaos

FULL 20d ago

Backups dbNexia_db

FULL 20d ago

Disk ANNAT 1

11.7 GB free (29.2%) of 40.0 GB.

Logs 66 Errors

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

Logs 55 Timeouts

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

Logs 1 Login failures

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

Logs 1 Memory grants

2026-10-17 09:41 - (@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 10.0%, memory free 41.8%, users 2, transactions 11.

TempDB Data and log

Data 22.4%, log 24.7%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-10-17 11:00, last failed -. 2 backup risks. Worst disk ANNAT 1 11.7 GB (29.2%). 123 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 10.0% / 41.8%
TempDB data / log 22.4% / 24.7%
Growth now / 7d forecast 0.0 GB / 0.0 GB
Runtime / 24h forecast 123 / 123
Backups / disks / jobs 2 / 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 1.89 GB
Last OK 2026-10-17 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 123 events

Errors 66, timeouts 55, 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 66, timeouts 55, 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 66, timeouts 55, 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 risks2
DBAChaos480/100

FULL 20d 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_db480/100

FULL 20d 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.

Storage1 low volumes
ANNAT 111.7 GB free

29.2% 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_db5.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-17 11:00
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; 2766 log/runtime events were recorded, latest at 2026-10-17 09:41; 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,766 runtime events over the next 24 hours. Pressure indicators: 2,766 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
2766 Logs
0 Locks
0 Queries
0 Gaps
2 disk 2766 log/runtime
Concrete findings 11
Disk ANNAT 1

11.7 GB free (29.2%) of 40.0 GB.

Disk ANNAT 1

11.7 GB free (29.2%) of 40.0 GB.

Logs 2,723 Errors

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

Logs 41 Timeouts

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

Logs 1 Login failures

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

Logs 1 Memory grants

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

Growth DOM_ThunderMoon_622B

0.0 GB growth (Log ).

Largest DB DOM_ThunderMoon_622B

0.1 GB current size.

Largest DB DOM_DreamBlossom_D66E

0.1 GB current size.

Resources CPU and memory

CPU 10.0%, memory free 41.8%, users 3, transactions 8.

TempDB Data and log

Data 1.3%, log 25.6%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-10-17 11:00, last failed -. Worst disk ANNAT 1 11.7 GB (29.2%). 2766 runtime events. 0.0 GB growth. CPU 10.0%, memory free 41.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,766 runtime events over the next 24 hours.
Break the trend recover or extend disk capacity; triage latest log errors.
CPU / memory free 10.0% / 41.8%
TempDB data / log 1.3% / 25.6%
Growth now / 7d forecast 0.0 GB / 0.1 GB
Runtime / 24h forecast 2766 / 2766
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 3.58 GB
Last OK 2026-10-17 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 2766 events

Errors 2,723, timeouts 41, 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,723, timeouts 41, 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,723, timeouts 41, 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.

Storage2 low volumes
ANNAT 111.7 GB free

29.2% 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 111.7 GB free

29.2% 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
DOM_ThunderMoon_622B15.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_ThunderMoon_622B0.1 GB

Current largest database inventory sample.

DOM_DreamBlossom_D66E0.1 GB

Current largest database inventory sample.

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

Action

SERVER 4

TESTSRV_4.DBNEXIA.COM / Test / SQL Server / Last seen 2026-10-17 11:00
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; 83 log/runtime events were recorded, latest at 2026-10-17 09:41; 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 83 runtime events over the next 24 hours. Pressure indicators: 83 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
83 Logs
0 Locks
0 Queries
0 Gaps
2 disk 83 log/runtime
Concrete findings 9
Disk ANNAT 1

11.7 GB free (29.2%) of 40.0 GB.

Disk ANNAT 1

11.7 GB free (29.2%) of 40.0 GB.

Logs 42 Errors

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

Logs 41 Timeouts

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

Growth DBAChaos

0.0 GB growth (Log ).

Largest DB DBAChaos

0.1 GB current size.

Largest DB dbNexia_db

0.0 GB current size.

Resources CPU and memory

CPU 10.0%, memory free 41.8%, users 3, transactions 9.

TempDB Data and log

Data 3.2%, log 22.5%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-10-17 11:00, last failed -. Worst disk ANNAT 1 11.7 GB (29.2%). 83 runtime events. 0.0 GB growth. CPU 10.0%, memory free 41.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 83 runtime events over the next 24 hours.
Break the trend recover or extend disk capacity; triage latest log errors.
CPU / memory free 10.0% / 41.8%
TempDB data / log 3.2% / 22.5%
Growth now / 7d forecast 0.0 GB / 0.1 GB
Runtime / 24h forecast 83 / 83
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-17 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 83 events

Errors 42, timeouts 41, 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 42, timeouts 41, 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 42, timeouts 41, 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 111.7 GB free

29.2% 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 111.7 GB free

29.2% 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
DBAChaos10.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.1 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 -
Health91
Pressure13
TrendNeeds watching
DirectionEarly signal
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: No dominant problem pattern in the collected signals.

Dashboard Report
What happened

In the selected window, 1 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: 1 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 Early signal
0 Backups
0 Disk
0 Jobs
0 Logs
1 Locks
0 Queries
0 Gaps
1 blocking
Concrete findings 1
Deadlocks master

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

Metrics and evidence Signals

1 deadlocks / 0 blocking.

Recommended action Identify blockers, statements, and transaction order; prioritize indexing or code changes.
Pattern No dominant problem pattern in the collected signals.
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 1 / 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 concurrency1 signals
Deadlock2026-10-16 11:20

master; <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-10-16T11:20:19.806Z"><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.