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

No growth.

Health
  • CPU 1.0% Mem free 31.3% 3 sessions 9 trans
Error Pulse

No errors.

TempDB
  • DATA: 9.8 / 64.0 MB (15.2%)
    LOG  : 1.6 / 8.0 MB (20.4%)
SQL Agent Failures
  • dbNexia_Process_Logs / ServerMetrics
    2026-07-04 07:35:00
    Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplicate key in object 'db...
    Meaning

    job 'dbNexia_Process_Logs' failed because data handled by step 'ServerMetrics' violates a table rule or column limit.

    Impact

    Retrying without correcting the data or transformation usually fails again with the same message.

    Recommended fix

    Use the object/column/key named in the error message. Correct the source data, mapping, or target column size before rerunning the job.

    Verify

    The rerun should process the same batch without constraint, duplicate key, or truncation errors.

  • MAL_MAINT_Process_Logs / ServerMetrics
    2026-07-04 07:10:00
    Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplicate key in object 'db...
    Meaning

    job 'MAL_MAINT_Process_Logs' failed because data handled by step 'ServerMetrics' violates a table rule or column limit.

    Impact

    Retrying without correcting the data or transformation usually fails again with the same message.

    Recommended fix

    Use the object/column/key named in the error message. Correct the source data, mapping, or target column size before rerunning the job.

    Verify

    The rerun should process the same batch without constraint, duplicate key, or truncation errors.

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

No blocking reports.