SQL Server error log medium severity alert


The Error Log Medium Severity alert notifies you when its configured condition is met on SQL Server instances so you can investigate and respond.

Screenshot pending: Mini DBA SQL Server Error Log Medium Severity alert screenshot placeholder

Alert summary

  • Platform: SQL Server
  • Alert category: General
  • Default enabled: true
  • Default evaluation frequency: Minute

What Mini DBA checks

Mini DBA describes this alert as: Errors in the Sql Server error log of severity 15 or 16 These levels of severity covers user correctable errors such as problems with High Availability Groups or queries that throw errors Mini DBA evaluates this alert once a minute so changes are detected quickly.

How this alert helps

This alert surfaces new SQL Server error-log entries at the configured severity so engine, availability, resource, and user-correctable errors are investigated with their actual message and context.

When to enable it

Enable it on production and shared SQL Server instances. Route high-severity entries urgently, and tune medium-severity routing only after reviewing the error numbers and workload context that recur in the environment.

Threshold guidance

This alert is based on a state or event rather than a numeric threshold. Tune its schedule, scope, severity, and notification route so that the response matches the importance of the instance.

Remediation for an active alert

Open the exact SQL Server error-log entry, capture its error number, severity, state, timestamp, and surrounding messages, then follow the response for that specific condition. Check related availability, storage, job, and application evidence instead of treating the log itself as a disk-capacity problem.

Investigation workflow

  1. Record the error number, severity, state, message, timestamp, and affected database or session.
  2. Review surrounding SQL Server error-log entries and correlate them with jobs, availability events, deployments, and user reports.
  3. Resolve or escalate the specific SQL Server condition using the appropriate runbook.
  4. Confirm that the error is no longer recurring before adjusting alert routing.

Avoiding alert noise

Tune routing by error number, recurrence, and business impact rather than suppressing the whole error-log alert. Preserve visibility for new or high-severity errors even when a known benign message is handled separately.

Related pages