Action Center

One queue for operational work

Prioritized actions from connectivity, backups, storage, jobs, runtime signals, concurrency and telemetry gaps.

2026-10-14 14:21 24h lookback
Critical11
High27
Watch0
Due now/today38
Affected servers6
Total servers5
Severity shape38 open
Critical
11
High
27
Watch
0
Work categoriestop drivers
Backup
16
Storage
13
Runtime
5
Concurrency
4
Immediacy38 due now/today
38 immediate 0 planned
Owner loadassignment view
DBA
33
DBA / App owner
5
SLA bucketsplanning pressure
Today
38
Source pageswhere to investigate
Backup Readiness 16 Forecast 13 AI Incidents 9
Priority queue38 open signals
High808
DOM_DreamStone_5722 backup chain needs attention Backup

FULL 17d ago, LOG 400h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_DreamStone_5722 backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High808
DOM_ForestEcho_B4A4 backup chain needs attention Backup

FULL 17d ago, LOG 400h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ForestEcho_B4A4 backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High808
DOM_ForestSky_5A7D backup chain needs attention Backup

FULL 17d ago, LOG 400h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ForestSky_5A7D backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High808
DOM_ShadowRiver_9AF6 backup chain needs attention Backup

FULL 17d ago, LOG 400h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ShadowRiver_9AF6 backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High808
DOM_WhisperEcho_929E backup chain needs attention Backup

FULL 17d ago, LOG 400h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_WhisperEcho_929E backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
High808
DOM_CrystalStone_911A backup chain needs attention Backup

FULL 17d ago, LOG 400h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_CrystalStone_911A backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
High808
DOM_FlameCrystal_07F4 backup chain needs attention Backup

FULL 17d ago, LOG 400h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_FlameCrystal_07F4 backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
High808
DOM_MoonCrystal_16FD backup chain needs attention Backup

FULL 17d ago, LOG 400h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_MoonCrystal_16FD backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
High808
DOM_ShadowMoon_946A backup chain needs attention Backup

FULL 17d ago, LOG 400h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ShadowMoon_946A backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
High808
DOM_ShadowOcean_4486 backup chain needs attention Backup

FULL 17d ago, LOG 400h ago. Full: 2026-09-27 02:00, diff: -, log: 2026-09-27 22:00.

Run or repair the log-backup job. If truncation still fails, check open transactions, AG/replication queues, broken full-backup chain and backup target errors.
Recovery point or restore chain can be outside policy.
Meaning

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

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DOM_ShadowOcean_4486 backup chain needs attention'. 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.

Rule: backup-log Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
Critical408
DBAChaos backup chain needs attention Backup

FULL 17d ago. Full: 2026-09-27 02:00, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'DBAChaos backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DBAChaos backup chain needs attention'. 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.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
Critical408
dbNexia_db backup chain needs attention Backup

FULL 17d ago. Full: 2026-09-27 02:00, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'dbNexia_db backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'dbNexia_db backup chain needs attention'. 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.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Backup Readiness
Critical408
DBAChaos backup chain needs attention Backup

FULL 17d ago. Full: 2026-09-27 02:00, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'DBAChaos backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DBAChaos backup chain needs attention'. 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.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
Critical408
dbNexia_db backup chain needs attention Backup

FULL 17d ago. Full: 2026-09-27 02:00, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'dbNexia_db backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'dbNexia_db backup chain needs attention'. 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.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Backup Readiness
Critical408
DBAChaos backup chain needs attention Backup

FULL 17d ago. Full: 2026-09-27 02:00, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'DBAChaos backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'DBAChaos backup chain needs attention'. 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.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_5.DBNEXIA.COM Backup Readiness
Critical408
dbNexia_db backup chain needs attention Backup

FULL 17d ago. Full: 2026-09-27 02:00, diff: -, log: -.

Run or repair the full-backup job, verify target path, SQL service-account permissions, retention cleanup and free space, then confirm a newer full backup row exists in msdb.
Recovery point or restore chain can be outside policy.
Meaning

database 'dbNexia_db backup chain needs attention' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'dbNexia_db backup chain needs attention'. 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.

Rule: backup-full Owner: DBA SLA: Today
TESTSRV_5.DBNEXIA.COM Backup Readiness
Critical90
Error pulse detected Runtime

Errors 2704, timeouts 40, login failures 1, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
Meaning

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'Error pulse detected'. 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.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_1.DBNEXIA.COM AI Incidents
Critical90
Error pulse detected Runtime

Errors 2623, timeouts 43, login failures 0, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
Meaning

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'Error pulse detected'. 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.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_2.DBNEXIA.COM AI Incidents
Critical90
Error pulse detected Runtime

Errors 2612, timeouts 36, login failures 0, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
Meaning

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'Error pulse detected'. 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.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_3.DBNEXIA.COM AI Incidents
Critical90
Error pulse detected Runtime

Errors 41, timeouts 40, login failures 0, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
Meaning

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'Error pulse detected'. 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.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_4.DBNEXIA.COM AI Incidents
Critical90
Error pulse detected Runtime

Errors 39, timeouts 39, login failures 0, CPU warnings 0. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...

Correlate with deployments, jobs and connection changes, then isolate the failing workload.
Repeated runtime failures can indicate active service degradation.
Meaning

database 'Error pulse detected' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'Error pulse detected'. 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.

Rule: error-pulse Owner: DBA / App owner SLA: Today
TESTSRV_5.DBNEXIA.COM AI Incidents
High78
ANNAT 1 is low on free space Storage

13.4 GB free (33.4%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_1.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

13.4 GB free (33.4%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_1.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

13.4 GB free (33.4%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_1.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

13.4 GB free (33.4%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

13.4 GB free (33.4%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_2.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

13.4 GB free (33.4%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

13.4 GB free (33.4%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

13.4 GB free (33.4%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_3.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

13.4 GB free (33.4%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_4.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

13.4 GB free (33.4%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_4.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

13.4 GB free (33.4%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_4.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

13.4 GB free (33.4%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_5.DBNEXIA.COM Forecast
High78
ANNAT 1 is low on free space Storage

13.4 GB free (33.4%) of 40.0 GB.

Check current free GB against expected database, log, tempdb and backup growth for the next maintenance window; clean/move files or request capacity before reserve is breached.
Database growth, tempdb, backups or logs can stop the workload.
Meaning

database 'ANNAT 1 is low on free space' needs a newer log backup in the SQL backup chain.

Impact

Point-in-time restore is weakened and the transaction log can keep growing if log backups are not completing.

Recommended fix

Run or repair the log-backup job for database 'ANNAT 1 is low on free space'. 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.

Rule: disk-gb Owner: DBA SLA: Today
TESTSRV_5.DBNEXIA.COM Forecast
High76
Deadlock detected Concurrency

2026-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><victimProcess ...

Capture the deadlock graph, identify both statements and objects, then fix index support or transaction order so code paths acquire locks consistently.
Users may see failed transactions and retry storms.
Meaning

job 'Deadlock detected' failed because the failing step waited too long or was selected as a deadlock/lock victim.

Impact

The job logic may be valid, but it is colliding with other workload or missing an index that would reduce lock duration.

Recommended fix

Open the long-running/blocking report for the same time window. If a blocking session is shown, resolve that transaction first; otherwise optimize the statement in the failing step or move the schedule away from the conflicting workload.

Verify

Test-run the job and confirm no blocking/deadlock signal appears in the same time window.

Rule: deadlock Owner: DBA SLA: Today
WIN-PN3T1M2LOOO AI Incidents
High76
Deadlock detected Concurrency

2026-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><victimProcess ...

Capture the deadlock graph, identify both statements and objects, then fix index support or transaction order so code paths acquire locks consistently.
Users may see failed transactions and retry storms.
Meaning

job 'Deadlock detected' failed because the failing step waited too long or was selected as a deadlock/lock victim.

Impact

The job logic may be valid, but it is colliding with other workload or missing an index that would reduce lock duration.

Recommended fix

Open the long-running/blocking report for the same time window. If a blocking session is shown, resolve that transaction first; otherwise optimize the statement in the failing step or move the schedule away from the conflicting workload.

Verify

Test-run the job and confirm no blocking/deadlock signal appears in the same time window.

Rule: deadlock Owner: DBA SLA: Today
WIN-PN3T1M2LOOO AI Incidents
High76
Deadlock detected Concurrency

2026-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><victimProcess ...

Capture the deadlock graph, identify both statements and objects, then fix index support or transaction order so code paths acquire locks consistently.
Users may see failed transactions and retry storms.
Meaning

job 'Deadlock detected' failed because the failing step waited too long or was selected as a deadlock/lock victim.

Impact

The job logic may be valid, but it is colliding with other workload or missing an index that would reduce lock duration.

Recommended fix

Open the long-running/blocking report for the same time window. If a blocking session is shown, resolve that transaction first; otherwise optimize the statement in the failing step or move the schedule away from the conflicting workload.

Verify

Test-run the job and confirm no blocking/deadlock signal appears in the same time window.

Rule: deadlock Owner: DBA SLA: Today
WIN-PN3T1M2LOOO AI Incidents
High76
Deadlock detected Concurrency

2026-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><victimProcess ...

Capture the deadlock graph, identify both statements and objects, then fix index support or transaction order so code paths acquire locks consistently.
Users may see failed transactions and retry storms.
Meaning

job 'Deadlock detected' failed because the failing step waited too long or was selected as a deadlock/lock victim.

Impact

The job logic may be valid, but it is colliding with other workload or missing an index that would reduce lock duration.

Recommended fix

Open the long-running/blocking report for the same time window. If a blocking session is shown, resolve that transaction first; otherwise optimize the statement in the failing step or move the schedule away from the conflicting workload.

Verify

Test-run the job and confirm no blocking/deadlock signal appears in the same time window.

Rule: deadlock Owner: DBA SLA: Today
WIN-PN3T1M2LOOO AI Incidents