Loaded 2026-08-07 05:59:57
Back to Overview
Server dashboard

SERVER 2

Focused health, workload, backup, capacity, and reliability signals for this SQL Server instance.

Action required
Lookback 24 h | 2026-08-07 05:59:57
CPU 1.0% latest sample
Memory free 62.8% 1 sessions
Action signals 15 7 backup | 0 disk | 0 jobs
Workload events 3114 3106 errors | 0 long running
Health gaugesAction required
1%
CPU
63%
Memory free
Signal mix3121 signals
Backup
7
Disk
0
Jobs
0
Runtime
3106
Concurrency
8
Long queries
0
Capacity profilegrowth and size
dbNexia_db
6 MB
dbNexia_db
0.9 GB
DOM_DreamStone_5722
0.1 GB
Data coverage This page separates verified clean states from missing source data.
EventLog ok AuditLog ok DbSizes ok ServerMetrics ok MsdbBackup ok MsdbAgent ok LiveRequests ok VolumeStats ok TempDb ok
Priority queue
What needs attention on this server
DOM_DreamStone_5722 backup risk FULL missing, LOG missing | Recovery FULL Backup DOM_ForestEcho_B4A4 backup risk FULL missing, LOG missing | Recovery FULL Backup DOM_ForestSky_5A7D backup risk FULL missing, LOG missing | Recovery FULL Backup DOM_ShadowRiver_9AF6 backup risk FULL missing, LOG missing | Recovery FULL Backup
Signal mix
Current workload posture
7 backup risks 0 disk risks 0 job failures 3106 errors/timeouts/logins 0 long running 8 deadlock/blocking
Top Growth (24h)
  • dbNexia_db (Log ):6.0 MB
Health
  • CPU 1.0% Mem free 62.8% 1 sessions 7 trans
Error Pulse
  • Open event - Err 2787 Timeouts 224 Logins 95 Grants 95
    2026-08-07 05:29:38 - (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ...
    Meaning

    database 'Login failures' needs a newer log backup in the SQL backup chain.

    Next step

    Run or repair the log-backup job for database 'Login failures'. If the log still cannot truncate, fix the specific blocker: open transaction, replication/AG send queue, backup target failure, or full-backup chain reset.

TempDB
  • DATA: 7.7 / 64.0 MB (12.0%)
    LOG  : 1.8 / 8.0 MB (22.3%)
Largest Databases
  • dbNexia_db : 923.0 MB
  • DOM_DreamStone_5722 : 84.0 MB
  • DOM_ShadowRiver_9AF6 : 67.0 MB
  • MAL_MAINT_DB_old : 65.0 MB
  • DOM_WhisperEcho_929E : 45.0 MB
  • DOM_ForestEcho_B4A4 : 42.0 MB
  • DOM_ForestSky_5A7D : 34.0 MB
  • tempdb : 10.0 MB
  • DBAChaos : 9.0 MB
Latest Audit Events
Low Free Space

All drives healthy.

SQL Agent Failures

No job failures.

Backup Risks
  • DOM_DreamStone_5722 (FULL)
    FULL: - | DIFF: - | LOG: -
    FULL missing, LOG missing
    Meaning

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

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

  • DOM_ForestEcho_B4A4 (FULL)
    FULL: - | DIFF: - | LOG: -
    FULL missing, LOG missing
    Meaning

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

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

  • DOM_ForestSky_5A7D (FULL)
    FULL: - | DIFF: - | LOG: -
    FULL missing, LOG missing
    Meaning

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

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

  • DOM_ShadowRiver_9AF6 (FULL)
    FULL: - | DIFF: - | LOG: -
    FULL missing, LOG missing
    Meaning

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

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

  • DOM_WhisperEcho_929E (FULL)
    FULL: - | DIFF: - | LOG: -
    FULL missing, LOG missing
    Meaning

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

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

  • DBAChaos (SIMPLE)
    FULL: - | DIFF: - | LOG: -
    FULL missing
    Meaning

    database 'DBAChaos' is outside backup freshness policy.

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

  • dbNexia_db (SIMPLE)
    FULL: - | DIFF: - | LOG: -
    FULL missing
    Meaning

    database 'dbNexia_db' is outside backup freshness policy.

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

Long Running

No active or recently completed slow queries longer than 60 seconds.

Deadlocks
  • 2026-08-07 05:00:13 | system_health
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T05:00:13.378Z"><data name="xml_report"><type...
    Meaning

    A deadlock occurred in the database in the event; SQL Server selected the session shown in the event or a related session as victim.

    Recommended fix

    Use the event text to identify the two statements and objects. Add the missing index or make both code paths update/read objects in a consistent order.

  • 2026-08-07 05:00:13 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T05:00:13.378Z"><data name="xml_report"><valu...
    Meaning

    A deadlock occurred in the database in the event; SQL Server selected the session shown in the event or a related session as victim.

    Recommended fix

    Use the event text to identify the two statements and objects. Add the missing index or make both code paths update/read objects in a consistent order.

  • 2026-08-07 05:00:13 | master | SPID 31
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T05:00:13.378Z"><data name="xml_report"><valu...
    Meaning

    A deadlock occurred in database 'master'; SQL Server selected session 31 or a related session as victim.

    Recommended fix

    Use the event text to identify the two statements and objects. Add the missing index or make both code paths update/read objects in a consistent order.

  • 2026-08-07 04:00:11 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T04:00:11.150Z"><data name="xml_report"><valu...
    Meaning

    A deadlock occurred in the database in the event; SQL Server selected the session shown in the event or a related session as victim.

    Recommended fix

    Use the event text to identify the two statements and objects. Add the missing index or make both code paths update/read objects in a consistent order.

  • 2026-08-07 04:00:11 | master | SPID 32
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T04:00:11.150Z"><data name="xml_report"><valu...
    Meaning

    A deadlock occurred in database 'master'; SQL Server selected session 32 or a related session as victim.

    Recommended fix

    Use the event text to identify the two statements and objects. Add the missing index or make both code paths update/read objects in a consistent order.

Blocking
  • 2026-08-07 05:59:57 | tempdb | WIN-PN3T1M2LOOO | SPID 75
    SPID 75 blocked by 76. Wait PAGELATCH_EX 0 ms. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate date...
    Meaning

    session 75 was involved in blocking on database 'tempdb'.

    Recommended fix

    Resolve the blocking transaction first. If the same statement repeats, add the index that lets it find rows faster or reduce the transaction scope around it.

  • 2026-08-06 21:01:13 | DBAChaos | WIN-PN3T1M2LOOO | SPID 19
    EXEC dbo.usp_Chaos_BlockedSession;
    Meaning

    session 19 was involved in blocking on database 'DBAChaos'.

    Recommended fix

    Resolve the blocking transaction first. If the same statement repeats, add the index that lets it find rows faster or reduce the transaction scope around it.

  • 2026-08-06 13:01:10 | DBAChaos | WIN-PN3T1M2LOOO | SPID 19
    EXEC dbo.usp_Chaos_BlockedSession;
    Meaning

    session 19 was involved in blocking on database 'DBAChaos'.

    Recommended fix

    Resolve the blocking transaction first. If the same statement repeats, add the index that lets it find rows faster or reduce the transaction scope around it.