Loaded 2026-07-04 07:39:19
Back to Overview
Server dashboard

SERVER 4

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

Action required
Lookback 24 h | 2026-07-04 07:39:19
CPU 1.0% latest sample
Memory free 31.3% 1 sessions
Action signals 3 1 backup | 0 disk | 0 jobs
Workload events 2 0 errors | 0 long running
Health gaugesAction required
1%
CPU
31%
Memory free
Signal mix3 signals
Backup
1
Disk
0
Jobs
0
Runtime
0
Concurrency
2
Long queries
0
Capacity profilegrowth and size
MAL_MAINT_DB
0.6 GB
tempdb
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
Signal mix
Current workload posture
1 backup risks 0 disk risks 0 job failures 0 errors/timeouts/logins 0 long running 2 deadlock/blocking
Top Growth (24h)

No growth.

Health
  • CPU 1.0% Mem free 31.3% 1 sessions 7 trans
Error Pulse

No errors.

TempDB
  • DATA: 5.4 / 64.0 MB (8.4%)
    LOG  : 1.1 / 8.0 MB (13.7%)
SQL Agent Failures

No job failures.

Backup Risks
  • 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

No deadlocks.

Blocking
  • 2026-07-04 07:39:19 | dbNexia_db | WIN-PN3T1M2LOOO | SPID 53
    SPID 53 blocked by 57. Wait PAGELATCH_EX 70 ms. (@TopN int,@H int) CREATE TABLE #Rows ( EventTime datetime2, Dat...
    Meaning

    session 53 was involved in blocking on database 'dbNexia_db'.

    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-07-04 07:39:19 | tempdb | WIN-PN3T1M2LOOO | SPID 56
    SPID 56 blocked by 57. Wait PAGELATCH_EX 63 ms. (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate dat...
    Meaning

    session 56 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.