Loaded 2026-08-12 11:58:53
Back to Overview
Server dashboard

SERVER 5

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

Action required
Lookback 24 h | 2026-08-12 11:58:53
CPU 2.0% latest sample
Memory free 64.0% 1 sessions
Action signals 8 2 backup | 0 disk | 0 jobs
Workload events 129 122 errors | 1 long running
Health gaugesAction required
2%
CPU
64%
Memory free
Signal mix131 signals
Backup
2
Disk
0
Jobs
0
Runtime
122
Concurrency
6
Long queries
1
Capacity profilegrowth and size
dbNexia_db
6 MB
dbNexia_db
0.5 GB
DBAChaos
0.0 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
DBAChaos backup risk FULL missing | Recovery SIMPLE Backup dbNexia_db backup risk FULL missing | Recovery SIMPLE Backup
Signal mix
Current workload posture
2 backup risks 0 disk risks 0 job failures 122 errors/timeouts/logins 1 long running 6 deadlock/blocking
Top Growth (24h)
  • dbNexia_db (Log ):6.0 MB
Health
  • CPU 2.0% Mem free 64.0% 1 sessions 10 trans
Error Pulse
  • Open event - Err 62 Timeouts 60 Logins 0
    2026-08-12 11:02:21 - The request failed to run because the batch is aborted, this can be caused by abort signal sent from client, or another request is running i...
    Meaning

    Clients or jobs waited longer than their command timeout.

    Next step

    Open the same time window in Long Running and Blocking. If there is no blocker, tune the slow statement or reduce the batch/report size before increasing timeout settings.

TempDB
  • DATA: 5.4 / 64.0 MB (8.4%)
    LOG  : 2.2 / 8.0 MB (27.0%)
Largest Databases
  • dbNexia_db : 496.0 MB
  • DBAChaos : 11.0 MB
  • tempdb : 10.0 MB
Latest Audit Events
Low Free Space

All drives healthy.

SQL Agent Failures

No job failures.

Backup Risks
  • 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
  • DBAChaos | 1m 11s | completed cached query
    UPDATE dbo.ChaosLock SET Payload = Payload + 1, ModifiedUtc = SYSUTCDATETIME() WHERE LockId = 3
    Meaning

    This request in database 'DBAChaos' has run for 71 seconds.

    Recommended fix

    Use the SQL text shown in this row as the target. Add or adjust the index that supports its WHERE/JOIN/ORDER BY columns, update stale statistics, or break the operation into smaller batches.

Deadlocks
  • 2026-08-12 07:00:08 | master | SPID 67
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-12T07:00:08.553Z"><data name="xml_report"><valu...
    Meaning

    A deadlock occurred in database 'master'; SQL Server selected session 67 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-12 07:00:08 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-12T07:00:08.553Z"><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-12 00:00:10 | master | SPID 44
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-12T00:00:10.539Z"><data name="xml_report"><valu...
    Meaning

    A deadlock occurred in database 'master'; SQL Server selected session 44 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-12 00:00:10 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-12T00:00:10.539Z"><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-11 22:00:14 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-11T22:00:14.587Z"><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.

Blocking
  • 2026-08-12 02: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.