SQL Server instance memory alert


The Instance Memory 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 Instance Memory alert screenshot placeholder

Alert summary

  • Platform: SQL Server
  • Alert category: Memory
  • Default enabled: false
  • Default evaluation frequency: Minute
  • Threshold label: Mb used
  • Unit: Mb

What Mini DBA checks

Mini DBA describes this alert as: Memory used by this instance (Mb) Use this alert to tell you if the allocated memory is actually being used or not while tuning memory settings Mini DBA evaluates this alert once a minute so changes are detected quickly.

How this alert helps

This alert helps detect memory pressure and cache efficiency problems. Low cache effectiveness or high memory pressure increases physical I/O, query latency, and the chance that a workload will become unstable during busy periods.

When to enable it

Enable it once the instance has a normal workload baseline. It is especially useful on busy OLTP, reporting, and integration systems where resource pressure can quickly become user-visible.

Threshold guidance

Threshold meaning: Mb used. Major threshold: 10000 Mb. Comparison direction: over. For an over-threshold alert, decreasing a threshold makes that severity fire sooner; increasing it tolerates more load or pressure. Set the minor threshold as an early-warning level and the major threshold at the highest acceptable value for the service.

Remediation for an active alert

Check memory configuration, cache hit indicators, top memory consumers, and host pressure. Remove unnecessary competing services, tune query memory grants or work areas, adjust engine memory settings, and add RAM or resize the service tier when the working set has outgrown the instance.

Investigation workflow

  1. Confirm the alert is still active and note the first seen time, affected instance, and severity.
  2. Review the top consumers, host counters, service tier or instance size, and recent workload changes in Mini DBA before changing configuration or ending sessions.
  3. Compare the current value with the normal baseline for the same time of day or maintenance window.
  4. Record the cause, corrective action, and whether thresholds or routing should be adjusted after the incident.

Avoiding alert noise

If this alert is noisy, check whether the workload naturally has short bursts. Raise the duration or threshold for expected batch windows, but keep a lower route for production systems where user-facing latency matters. Avoid simply disabling the alert until you know whether the noise is caused by threshold choice or by a real capacity trend.

Related pages