Operations overview

dbNexia Demo operations cockpit

Prioritized health, capacity, backup, job, and workload signals across registered SQL Server instances.

Action required
Lookback 24 h | 2026-07-04 06:26:46
Servers 5
Healthy 5
Unhealthy 0
Action signals 2781
Evidence coverage 100%
Estate postureAction required
5 healthy 0 unhealthy
Signal mix2781 active
Backup
20
Disk
0
Jobs
2
Runtime
2757
Concurrency
2
Long queries
0
Largest databasestop 5
MAL_MAINT_DB
0.9 GB
dbNexia_db
0.8 GB
MAL_MAINT_DB
0.8 GB
MAL_MAINT_DB
0.8 GB
MAL_MAINT_DB
0.6 GB
Growth pressure24h
TESTSRV_1.DBNEXIA.COM
12 MB
Data coverage 100% verified, 0 gaps across 0 servers. Empty panels are only marked clean when their source is available.
EventLog ok AuditLog ok DbSizes ok ServerMetrics ok MsdbBackup ok MsdbAgent ok LiveRequests ok VolumeStats ok TempDb ok
Priority queue
What needs attention first
Server Overview Open Forecast
TESTSRV_1.DBNEXIA.COM | DOM_BlossomWhisper_FDD3 backup risk FULL missing, LOG missing | Recovery FULL Backup TESTSRV_1.DBNEXIA.COM | DOM_DreamBlossom_D66E backup risk FULL missing, LOG missing | Recovery FULL Backup TESTSRV_1.DBNEXIA.COM | DOM_ForestDream_BD6D backup risk FULL missing, LOG missing | Recovery FULL Backup TESTSRV_1.DBNEXIA.COM | DOM_ShadowWhisper_67B1 backup risk FULL missing, LOG missing | Recovery FULL Backup TESTSRV_5.DBNEXIA.COM | dbNexia_Process_Logs ServerMetrics | 2026-07-04 06:20:00 Job TESTSRV_5.DBNEXIA.COM | MAL_MAINT_Process_Logs ServerMetrics | 2026-07-04 05:40:00 Job
Signal mix
Current workload posture
20 backup risks 0 disk risks 2 job failures 2757 errors/timeouts/logins 0 long running 2 deadlock/blocking
Top Growth (24h)
SQL Agent Failures
  • TESTSRV_5.DBNEXIA.COM - dbNexia_Process_Logs / ServerMetrics
    2026-07-04 06:20:00
    Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplica...
    Meaning

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

    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.

  • TESTSRV_5.DBNEXIA.COM - MAL_MAINT_Process_Logs / ServerMetrics
    2026-07-04 05:40:00
    Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplica...
    Meaning

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

    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.

Latest Audit Events
  • TESTSRV_4.DBNEXIA.COM - LGIF: Login failed for user 'MAL_MAINT_USER'. Reason: Failed to open the explicitly specified database 'MA
    2026-07-03 12:06:53
  • TESTSRV_3.DBNEXIA.COM - LGIF: Login failed for user 'MAL_MAINT_USER'. Reason: Failed to open the explicitly specified database 'MA
    2026-07-03 12:06:53
  • TESTSRV_5.DBNEXIA.COM - LGIF: Login failed for user 'MAL_MAINT_USER'. Reason: Failed to open the explicitly specified database 'MA
    2026-07-03 12:06:53
  • TESTSRV_1.DBNEXIA.COM - LGIF: Login failed for user 'MAL_MAINT_USER'. Reason: Failed to open the explicitly specified database 'MA
    2026-07-03 12:06:53
  • TESTSRV_2.DBNEXIA.COM - LGIF: Login failed for user 'MAL_MAINT_USER'. Reason: Failed to open the explicitly specified database 'MA
    2026-07-03 12:06:53
  • TESTSRV_5.DBNEXIA.COM - LGIF: Login failed for user 'MAL_MAINT_USER'. Reason: Failed to open the explicitly specified database 'MA
    2026-07-03 12:00:06
  • TESTSRV_4.DBNEXIA.COM - LGIF: Login failed for user 'MAL_MAINT_USER'. Reason: Failed to open the explicitly specified database 'MA
    2026-07-03 12:00:06
  • TESTSRV_3.DBNEXIA.COM - LGIF: Login failed for user 'MAL_MAINT_USER'. Reason: Failed to open the explicitly specified database 'MA
    2026-07-03 12:00:06
  • TESTSRV_2.DBNEXIA.COM - LGIF: Login failed for user 'MAL_MAINT_USER'. Reason: Failed to open the explicitly specified database 'MA
    2026-07-03 12:00:06
  • TESTSRV_1.DBNEXIA.COM - LGIF: Login failed for user 'MAL_MAINT_USER'. Reason: Failed to open the explicitly specified database 'MA
    2026-07-03 12:00:06
Largest Databases
Low Free Space

All drives healthy (>10% and >20 GB).

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

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

    Recommended fix

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

  • FULL: - | DIFF: - | LOG: -
    FULL missing, LOG missing
    Meaning

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

    Recommended fix

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

  • FULL: - | DIFF: - | LOG: -
    FULL missing, LOG missing
    Meaning

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

    Recommended fix

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

  • FULL: - | DIFF: - | LOG: -
    FULL missing, LOG missing
    Meaning

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

    Recommended fix

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

  • FULL: - | DIFF: - | LOG: -
    FULL missing, LOG missing
    Meaning

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

    Recommended fix

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

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

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

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

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

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

  • FULL: - | DIFF: - | LOG: -
    FULL missing, LOG missing
    Meaning

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

    Recommended fix

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

  • FULL: - | DIFF: - | LOG: -
    FULL missing, LOG missing
    Meaning

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

    Recommended fix

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

  • FULL: - | DIFF: - | LOG: -
    FULL missing, LOG missing
    Meaning

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

    Recommended fix

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

  • FULL: - | DIFF: - | LOG: -
    FULL missing, LOG missing
    Meaning

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

    Recommended fix

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

  • FULL: - | DIFF: - | LOG: -
    FULL missing, LOG missing
    Meaning

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

    Recommended fix

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

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

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

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

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

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

Blocking

No blocking reports.

TempDB Pressure
Long Running Queries

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

Server Health
Error Pulse
  • TESTSRV_1.DBNEXIA.COM - Err 988 | Timeouts 1 | Logins 0
    2026-07-03 23:47:16
    The specified @name ('MAL_MAINT_MAINT_JOB') already exists.
  • TESTSRV_3.DBNEXIA.COM - Err 891 | Timeouts 1 | Logins 0
    2026-07-03 21:30:03
    Conversion failed when converting the nvarchar value 'Updated_4204' to data type bit.
  • TESTSRV_2.DBNEXIA.COM - Err 876 | Timeouts 0 | Logins 0
    2026-07-03 21:30:04
    Conversion failed when converting the nvarchar value 'Updated_6959' to data type bit.
Deadlocks
  • TESTSRV_1.DBNEXIA.COM - 2026-07-03 11:55:15 | system_health
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-07-03T11:55:15.544Z"><data name="xml_report"><type...
  • TESTSRV_1.DBNEXIA.COM - 2026-07-03 11:55:15 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-07-03T11:55:15.544Z"><data name="xml_report"><valu...