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-07-04 08:37
Critical5
Action0
Watch0
Stable0
Open actions23
Runtime events2757
Telemetry gaps0
Growth0.0 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.
20
Capacity protection Low disk, database growth and projected pressure are visible before they become write failures.
0
Service reliability Failed jobs, runtime events, deadlocks, blocking and long-running queries are treated as connected reliability evidence.
2760
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 5

TESTSRV_5.DBNEXIA.COM / Test / SQL Server / Last seen 2026-07-04 08:35
Health76
Pressure36
TrendStable
DirectionNo negative trend
Best advice

P1 Backup: Repair backup chain for dbNexia_db and validate restore. This is first because current evidence indicates high restore risk; this must be fixed before a real incident. Pattern: SQL Agent jobs are failing repeatedly inside the selected review window.

Dashboard Report
What happened

In the selected window, 1 database backup chains crossed the configured risk threshold; 2 SQL Agent failures were captured.

What is happening

Right now, maintenance or business jobs need human follow-up; restore confidence is degraded.

What happens next

Restore risk will continue to increase until the broken backup chain is repaired and verified. Pressure indicators: 3 action signals. The likely outcome is operational impact or missed recovery objectives unless the first action is handled immediately.

Actions to break the trend 2
P1
Backup

Repair backup chain for dbNexia_db and validate restore.

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

Fix and rerun failed job: MAL_MAINT_Process_Logs.

Failed jobs leave maintenance, imports, or business data in an unknown state.
Trend and signal mix No negative trend
1 Backups
0 Disk
2 Jobs
0 Logs
0 Locks
0 Queries
0 Gaps
1 backup 2 job
Concrete findings 7
Backups dbNexia_db

FULL missing

Jobs MAL_MAINT_Process_Logs

2026-07-04 08:30 - ServerMetrics: Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplicate key in ...

Jobs dbNexia_Process_Logs

2026-07-04 07:50 - ServerMetrics: Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplicate key in ...

Largest DB MAL_MAINT_DB

0.6 GB current size.

Largest DB tempdb

0.0 GB current size.

Resources CPU and memory

CPU 1.0%, memory free 31.9%, users 1, transactions 7.

TempDB Data and log

Data 15.7%, log 18.2%, version store 0 MB.

Metrics and evidence Signals

Last OK 2026-07-04 08:35, last failed -. 1 backup risks. 2 job failures. CPU 1.0%, memory free 31.9%. TempDB data 15.7%, log 18.2%.

Recommended action Repair the backup chain now and validate restore coverage for the highest-risk databases.
Pattern SQL Agent jobs are failing repeatedly inside the selected review window.
Forecast Restore risk will continue to increase until the broken backup chain is repaired and verified.
Break the trend validate backup and restore path; fix failing SQL Agent jobs.
CPU / memory free 1.0% / 31.9%
TempDB data / log 15.7% / 18.2%
Growth now / 7d forecast 0.0 GB / 0.0 GB
Runtime / 24h forecast 0 / 0
Backups / disks / jobs 1 / 0 / 2
Blocking / long queries 0 / 0
Telemetry gaps 0
Largest database 0.6 GB
Operating profile Test
Type SQL Server
Environment Test
Repository size 1.33 GB
Last OK 2026-07-04 08:35
Last failed -
Data quality 100%
Source confidence 0 gaps
AuditLog Available

dbNexia_db.dbo.AuditLog

DbSizes Available

dbNexia_db.dbo.dbsizes

EventLog Available

dbNexia_db.dbo.EventLog

LiveRequests Available

VIEW SERVER STATE permission

MsdbAgent Available

msdb SQL Agent history

MsdbBackup Available

msdb.dbo.backupset

ServerMetrics Available

dbNexia_db.dbo.ServerMetrics

TempDb Available

VIEW SERVER STATE permission

VolumeStats Available

VIEW SERVER STATE permission

Runtime 0 events

No runtime event sample was loaded for this server.

No latest runtime message captured.

Meaning

database 'No runtime event sample was loaded for this server.' needs a newer log backup in the SQL backup chain.

Recommended fix

Run or repair the log-backup job for database 'No runtime event sample was loaded for this server.'. 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 risks1
dbNexia_db180/100

FULL missing

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.

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

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

Largest databases and job failures2 job failures
MAL_MAINT_DB0.6 GB

Current largest database inventory sample.

tempdb0.0 GB

Current largest database inventory sample.

MAL_MAINT_Process_Logs2026-07-04 08:30

ServerMetrics: Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplicate key in ...

Meaning and fix

Meaning: job 'MAL_MAINT_Process_Logs' failed because data handled by the failing step violates a table rule or column limit.

Fix: Use the object/column/key named in the error message. Correct the source data, mapping, or target column size before rerunning the job.

Verify: The rerun should process the same batch without constraint, duplicate key, or truncation errors.

dbNexia_Process_Logs2026-07-04 07:50

ServerMetrics: Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplicate key in ...

Meaning and fix

Meaning: job 'dbNexia_Process_Logs' failed because data handled by the failing step violates a table rule or column limit.

Fix: Use the object/column/key named in the error message. Correct the source data, mapping, or target column size before rerunning the job.

Verify: The rerun should process the same batch without constraint, duplicate key, or truncation errors.