Operations

dbNexia Demo Operations Cockpit

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

Action required
Lookback 24 h | 2026-08-07 05:03:33
Servers 5
Healthy 5
Unhealthy 0
Action signals 9879
Evidence coverage 100%
Estate postureAction required
5 healthy 0 unhealthy
Signal mix9879 active
Backup
25
Disk
0
Jobs
0
Runtime
9817
Concurrency
35
Long queries
2
Largest databasestop 5
dbNexia_db
1.0 GB
dbNexia_db
0.9 GB
dbNexia_db
0.9 GB
dbNexia_db
0.5 GB
dbNexia_db
0.5 GB
Growth pressure24h
TESTSRV_3.DBNEXIA.COM
8 MB
TESTSRV_4.DBNEXIA.COM
8 MB
TESTSRV_5.DBNEXIA.COM
6 MB
TESTSRV_2.DBNEXIA.COM
6 MB
TESTSRV_1.DBNEXIA.COM
4 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
Signal mix
Current workload posture
25 backup risks 0 disk risks 0 job failures 9817 errors/timeouts/logins 2 long running 35 deadlock/blocking
Top Growth (24h)
SQL Agent Failures

No job failures in the current lookback.

Latest Audit Events
  • TESTSRV_3.DBNEXIA.COM - LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th
    2026-08-07 04:05:01
  • TESTSRV_3.DBNEXIA.COM - LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th
    2026-08-07 04:05:01
  • TESTSRV_4.DBNEXIA.COM - LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th
    2026-08-07 04:05:01
  • TESTSRV_2.DBNEXIA.COM - LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th
    2026-08-07 04:05:01
  • TESTSRV_2.DBNEXIA.COM - LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th
    2026-08-07 04:05:01
  • TESTSRV_1.DBNEXIA.COM - LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th
    2026-08-07 04:05:01
  • TESTSRV_1.DBNEXIA.COM - LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th
    2026-08-07 04:05:01
  • TESTSRV_5.DBNEXIA.COM - LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th
    2026-08-07 04:05:01
  • TESTSRV_4.DBNEXIA.COM - LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th
    2026-08-07 04:05:01
  • TESTSRV_5.DBNEXIA.COM - LGIF: Login failed. The login is from an untrusted domain and cannot be used with Integrated authenticatio
    2026-08-07 04:05:01
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 '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.

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

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

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

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

  • 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
  • TESTSRV_5.DBNEXIA.COM - 2026-08-07 01:01:09 | 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.

  • TESTSRV_3.DBNEXIA.COM - 2026-08-06 22:01:17 | 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.

  • TESTSRV_2.DBNEXIA.COM - 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.

  • TESTSRV_4.DBNEXIA.COM - 2026-08-06 18:01:09 | 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.

  • TESTSRV_3.DBNEXIA.COM - 2026-08-06 14:01:16 | 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.

  • TESTSRV_1.DBNEXIA.COM - 2026-08-06 13:01:15 | DBAChaos | WIN-PN3T1M2LOOO | SPID 20
    EXEC dbo.usp_Chaos_BlockedSession;
    Meaning

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

  • TESTSRV_2.DBNEXIA.COM - 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.

  • TESTSRV_3.DBNEXIA.COM - 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.

  • TESTSRV_4.DBNEXIA.COM - 2026-08-06 11:01:15 | 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.

  • TESTSRV_5.DBNEXIA.COM - 2026-08-06 09:01:12 | 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.

TempDB Pressure
Long Running Queries
  • TESTSRV_1.DBNEXIA.COM – 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.

  • TESTSRV_3.DBNEXIA.COM – 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.

Server Health
Error Pulse
  • TESTSRV_1.DBNEXIA.COM - Err 2895 | Timeouts 217 | Logins 94 | CPU 0 | Grants 94
    2026-08-07 04:25:31
    (@Lookback int) IF DB_ID(N'dbNexia_DB') IS NULL OR OBJECT_ID(N'dbNexia_DB.dbo.EventLog') IS NULL BEGIN SELECT Errors = CAST(NULL AS int), Timeouts = CAST(NUL...
  • TESTSRV_2.DBNEXIA.COM - Err 2783 | Timeouts 219 | Logins 93 | CPU 0 | Grants 93
    2026-08-07 04:25:31
    (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...
  • TESTSRV_3.DBNEXIA.COM - Err 2717 | Timeouts 231 | Logins 102 | CPU 0 | Grants 102
    2026-08-07 04:25:31
    (@Lookback int) IF DB_ID(N'dbNexia_DB') IS NULL OR OBJECT_ID(N'dbNexia_DB.dbo.EventLog') IS NULL BEGIN SELECT Errors = CAST(NULL AS int), Timeouts = CAST(NUL...
  • TESTSRV_5.DBNEXIA.COM - Err 114 | Timeouts 120 | Logins 1
    2026-08-07 04:25:31
    (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...
  • TESTSRV_4.DBNEXIA.COM - Err 112 | Timeouts 118 | Logins 1 | CPU 0 | Grants 1
    2026-08-07 04:25:31
    (@MinEvidenceTime datetime) CREATE TABLE #SqlBackupLog ( LogDate datetime NULL, ProcessInfo nvarchar(64) NULL, [Text] nvarchar(max) NULL ); DECLARE @LogNumb...
Deadlocks
  • TESTSRV_2.DBNEXIA.COM - 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...
  • TESTSRV_2.DBNEXIA.COM - 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...
  • TESTSRV_5.DBNEXIA.COM - 2026-08-07 05:00:11 | system_health
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T05:00:11.437Z"><data name="xml_report"><type...
  • TESTSRV_5.DBNEXIA.COM - 2026-08-07 05:00:11 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T05:00:11.437Z"><data name="xml_report"><valu...
  • TESTSRV_5.DBNEXIA.COM - 2026-08-07 04:00:11 | master | SPID 2
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T04:00:11.793Z"><data name="xml_report"><valu...
  • TESTSRV_5.DBNEXIA.COM - 2026-08-07 04:00:11 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T04:00:11.793Z"><data name="xml_report"><valu...
  • TESTSRV_2.DBNEXIA.COM - 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...
  • TESTSRV_2.DBNEXIA.COM - 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...
  • TESTSRV_3.DBNEXIA.COM - 2026-08-07 04:00:08 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T04:00:08.027Z"><data name="xml_report"><valu...
  • TESTSRV_3.DBNEXIA.COM - 2026-08-07 04:00:08 | master | SPID 68
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T04:00:08.027Z"><data name="xml_report"><valu...
  • TESTSRV_3.DBNEXIA.COM - 2026-08-07 03:00:07 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T03:00:07.778Z"><data name="xml_report"><valu...
  • TESTSRV_3.DBNEXIA.COM - 2026-08-07 03:00:07 | master | SPID 41
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T03:00:07.778Z"><data name="xml_report"><valu...
  • TESTSRV_5.DBNEXIA.COM - 2026-08-07 02:00:10 | master | SPID 3
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T02:00:10.862Z"><data name="xml_report"><valu...
  • TESTSRV_2.DBNEXIA.COM - 2026-08-07 02:00:09 | master | SPID 71
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T02:00:09.985Z"><data name="xml_report"><valu...
  • TESTSRV_4.DBNEXIA.COM - 2026-08-07 01:00:08 | master | SPID 49
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T01:00:08.256Z"><data name="xml_report"><valu...
  • TESTSRV_4.DBNEXIA.COM - 2026-08-07 01:00:08 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-07T01:00:08.256Z"><data name="xml_report"><valu...
  • TESTSRV_4.DBNEXIA.COM - 2026-08-06 23:00:12 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-06T23:00:12.074Z"><data name="xml_report"><valu...
  • TESTSRV_4.DBNEXIA.COM - 2026-08-06 23:00:12 | master | SPID 42
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-06T23:00:12.074Z"><data name="xml_report"><valu...
  • TESTSRV_3.DBNEXIA.COM - 2026-08-06 23:00:08 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-06T23:00:08.590Z"><data name="xml_report"><valu...
  • TESTSRV_4.DBNEXIA.COM - 2026-08-06 22:00:08 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-06T22:00:08.370Z"><data name="xml_report"><valu...
  • TESTSRV_1.DBNEXIA.COM - 2026-08-06 22:00:07 | master | SPID 65
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-06T22:00:07.379Z"><data name="xml_report"><valu...
  • TESTSRV_1.DBNEXIA.COM - 2026-08-06 22:00:07 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-06T22:00:07.379Z"><data name="xml_report"><valu...
  • TESTSRV_1.DBNEXIA.COM - 2026-08-06 14:00:11 | system_health file
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-06T14:00:11.087Z"><data name="xml_report"><valu...
  • TESTSRV_1.DBNEXIA.COM - 2026-08-06 14:00:11 | master | SPID 47
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-06T14:00:11.087Z"><data name="xml_report"><valu...
  • TESTSRV_1.DBNEXIA.COM - 2026-08-06 12:00:11 | master | SPID 4
    <event name="xml_deadlock_report" package="sqlserver" timestamp="2026-08-06T12:00:11.025Z"><data name="xml_report"><valu...