SERVER 1
TESTSRV_1.DBNEXIA.COM / Test / SQL Server / Last seen 2026-10-14 15:15P2 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.
In the selected window, 2 volumes dropped below free-space policy; 2764 log/runtime events were recorded, latest at 2026-10-14 15:03; databases grew by 0.0 GB in the selected window.
Right now, the error/log stream is active; storage headroom is below policy.
The current log pace projects to about 2,764 runtime events over the next 24 hours. Pressure indicators: 2,764 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.
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.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.12.9 GB free (32.2%) of 40.0 GB.
12.9 GB free (32.2%) of 40.0 GB.
2026-10-14 15:03 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...
2026-10-14 15:03 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...
2026-10-14 15:03 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...
2026-10-14 15:03 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLAR...
0.0 GB growth (Log ).
0.1 GB current size.
0.1 GB current size.
CPU 12.0%, memory free 39.1%, users 2, transactions 8.
Data 1.5%, log 10.4%, version store 0 MB.
Last OK 2026-10-14 15:15, last failed -. Worst disk ANNAT 1 12.9 GB (32.2%). 2764 runtime events. 0.0 GB growth. CPU 12.0%, memory free 39.1%.
dbNexia_db.dbo.AuditLog
dbNexia_db.dbo.dbsizes
dbNexia_db.dbo.EventLog
VIEW SERVER STATE permission
msdb SQL Agent history
msdb.dbo.backupset
dbNexia_db.dbo.ServerMetrics
VIEW SERVER STATE permission
VIEW SERVER STATE permission
Errors 2,713, timeouts 49, 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...
database 'Errors 2,713, timeouts 49, login failures 1, CPU warnings 0, memory grants 1.' needs a newer log backup in the SQL backup chain.
Run or repair the log-backup job for database 'Errors 2,713, timeouts 49, 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.
Open Backup History for the database and confirm a newer successful backup row of the missing type appears after the fix.
No backup risks detected for this server.
32.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.
32.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.
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.
No long running, blocking, or deadlock signals detected in this window.
Current largest database inventory sample.
Current largest database inventory sample.
Current largest database inventory sample.
Current largest database inventory sample.
Current largest database inventory sample.
Current largest database inventory sample.
No SQL Agent job failures detected in this window.