SERVER 5
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)
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%)
Largest Databases
- MAL_MAINT_DB : 585.0 MB
- tempdb : 4.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:57 -
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
-
dbNexia_Process_Logs
/ ServerMetrics
2026-07-04 07:35:00Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplicate key in object 'db...Meaningjob 'dbNexia_Process_Logs' failed because data handled by step 'ServerMetrics' violates a table rule or column limit.
ImpactRetrying without correcting the data or transformation usually fails again with the same message.
Recommended fixUse the object/column/key named in the error message. Correct the source data, mapping, or target column size before rerunning the job.
VerifyThe rerun should process the same batch without constraint, duplicate key, or truncation errors.
-
MAL_MAINT_Process_Logs
/ ServerMetrics
2026-07-04 07:10:00Executed as user: NT SERVICE\SQLAgent$TESTINST5. Violation of PRIMARY KEY constraint 'PK__ServerMe__997AE428B421C51A'. Cannot insert duplicate key in object 'db...Meaningjob 'MAL_MAINT_Process_Logs' failed because data handled by step 'ServerMetrics' violates a table rule or column limit.
ImpactRetrying without correcting the data or transformation usually fails again with the same message.
Recommended fixUse the object/column/key named in the error message. Correct the source data, mapping, or target column size before rerunning the job.
VerifyThe rerun should process the same batch without constraint, duplicate key, or truncation errors.
Backup Risks
-
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
No deadlocks.
Blocking
No blocking reports.