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-15 17:17
Critical3
Action2
Watch0
Stable0
Open actions26
Runtime events7931
Telemetry gaps0
Growth0.1 GB
Operational impact 0 / 100 High exposure ยท evidence coverage 100%
Recovery readiness Backup chains, restore confidence and failed maintenance are folded into each server's actions.
16
Capacity protection Low disk, database growth and projected pressure are visible before they become write failures.
10
Service reliability Failed jobs, runtime events, deadlocks, blocking and long-running queries are treated as connected reliability evidence.
7931
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-15 17:15
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; 2574 log/runtime events were recorded, latest at 2026-10-15 15:30; 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,574 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
2574 Logs
0 Locks
0 Queries
0 Gaps
7 backup 2 disk 2574 log/runtime
Concrete findings 12
Backups DOM_DreamStone_5722

FULL 18d ago, LOG 427h ago

Backups DOM_ForestEcho_B4A4

FULL 18d ago, LOG 427h ago

Backups DOM_ForestSky_5A7D

FULL 18d ago, LOG 427h ago

Disk ANNAT 1

12.3 GB free (30.8%) of 40.0 GB.

Disk ANNAT 1

12.3 GB free (30.8%) of 40.0 GB.

Logs 2,565 Errors

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

Logs 9 Timeouts

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

Growth DOM_ForestSky_5A7D

0.0 GB growth (Log ).

Largest DB DOM_WhisperEcho_929E

0.5 GB current size.

Largest DB DOM_ShadowRiver_9AF6

0.5 GB current size.

Resources CPU and memory

CPU 19.0%, memory free 36.2%, users 2, transactions 8.

TempDB Data and log

Data 1.1%, log 39.0%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-10-15 17:15, last failed -. 7 backup risks. Worst disk ANNAT 1 12.3 GB (30.8%). 2574 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 19.0% / 36.2%
TempDB data / log 1.1% / 39.0%
Growth now / 7d forecast 0.0 GB / 0.1 GB
Runtime / 24h forecast 2574 / 2574
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-15 17:15
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 2574 events

Errors 2,565, timeouts 9, 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,565, timeouts 9, 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,565, timeouts 9, 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_5722859/100

FULL 18d ago, LOG 427h 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_B4A4859/100

FULL 18d ago, LOG 427h 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_5A7D859/100

FULL 18d ago, LOG 427h 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_9AF6859/100

FULL 18d ago, LOG 427h 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_929E859/100

FULL 18d ago, LOG 427h 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.

DBAChaos432/100

FULL 18d 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_db432/100

FULL 18d 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 112.3 GB free

30.8% 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 112.3 GB free

30.8% 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_ForestSky_5A7D13.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.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.

dbNexia_db0.0 GB

Current largest database inventory sample.

tempdb0.0 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.