SERVER 1
Focused health, workload, backup, capacity, and reliability signals for this SQL Server instance.
What needs attention on this server
Current workload posture
Top Growth (24h)
- tempdb (Log ):12.0 MB
Health
- CPU 1.0% Mem free 31.3% 1 sessions 7 trans
Error Pulse
-
Open event
-
Err 988
Timeouts 1
Logins 0
2026-07-03 23:47:16 - The specified @name ('MAL_MAINT_MAINT_JOB') already exists.Meaning
Clients or jobs waited longer than their command timeout.
Next stepOpen 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: 11.9 / 576.0 MB (2.1%)LOG : 31.5 / 136.0 MB (23.2%)
Largest Databases
- dbNexia_db : 861.0 MB
- MAL_MAINT_DB : 825.0 MB
- MAL_MAINT_DB_old : 111.0 MB
- DOM_ForestDream_BD6D : 79.0 MB
- DOM_DreamBlossom_D66E : 58.0 MB
- DOM_ShadowWhisper_67B1 : 53.0 MB
- DOM_ThunderMoon_622B : 36.0 MB
- tempdb : 29.0 MB
- DOM_BlossomWhisper_FDD3 : 22.0 MB
Latest Audit Events
-
LGIF: Login failed for user 'MAL_MAINT_USER'. Reason: Failed to open the explicitly specified database 'MA
2026-07-03 12:06:53 -
LGIF: Login failed for user 'MAL_MAINT_USER'. Reason: Failed to open the explicitly specified database 'MA
2026-07-03 12:00:06 -
LGIF: Login failed for user 'MAL_MAINT_USER'. Reason: Failed to open the explicitly specified database 'MA
2026-07-03 11:59:56 -
LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th
2026-07-03 04:05:01 -
LGIF: Network error code 0x6d occurred while establishing a connection; the connection has been closed. Th
2026-07-03 04:05:01
Low Free Space
All drives healthy.
SQL Agent Failures
No job failures.
Backup Risks
-
DOM_BlossomWhisper_FDD3
(FULL)
FULL: - | DIFF: - | LOG: -FULL missing, LOG missingMeaning
database 'DOM_BlossomWhisper_FDD3' needs a newer log backup in the SQL backup chain.
Recommended fixRun 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.
-
DOM_DreamBlossom_D66E
(FULL)
FULL: - | DIFF: - | LOG: -FULL missing, LOG missingMeaning
database 'DOM_DreamBlossom_D66E' needs a newer log backup in the SQL backup chain.
Recommended fixRun 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.
-
DOM_ForestDream_BD6D
(FULL)
FULL: - | DIFF: - | LOG: -FULL missing, LOG missingMeaning
database 'DOM_ForestDream_BD6D' needs a newer log backup in the SQL backup chain.
Recommended fixRun 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.
-
DOM_ShadowWhisper_67B1
(FULL)
FULL: - | DIFF: - | LOG: -FULL missing, LOG missingMeaning
database 'DOM_ShadowWhisper_67B1' needs a newer log backup in the SQL backup chain.
Recommended fixRun 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.
-
DOM_ThunderMoon_622B
(FULL)
FULL: - | DIFF: - | LOG: -FULL missing, LOG missingMeaning
database 'DOM_ThunderMoon_622B' needs a newer log backup in the SQL backup chain.
Recommended fixRun 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.
-
dbNexia_db
(SIMPLE)
FULL: - | DIFF: - | LOG: -FULL missingMeaning
database 'dbNexia_db' is outside backup freshness policy.
Recommended fixRun 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
-
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...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 fixUse 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
No blocking reports.