SQL Server Agent Alerts: Balancing Alert Thresholds and Notification Noise

Goal

Configure SQL Server Agent alerts to deliver actionable notifications without overwhelming operators.

Constraints

SQL Server Agent alerts use sp_add_alert with severity or performance‑counter thresholds, but lack native rate‑limit or deduplication. Operators are defined in msdb.dbo.sysoperators and require Database Mail profiles; permission boundaries are enforced by the sysadmin role or DatabaseMailUserRole.

Uncertainty

It is unclear how best to select thresholds that filter noise while still capturing critical events, whether to supplement native alerts with external suppression logic, and how to restrict notification recipients without breaking essential alert delivery.

Questions

• What threshold configurations for sp_add_alert effectively reduce duplicate alerts while preserving high‑severity events?
• Which permissions must be granted to operators to receive alerts, and how can we restrict notification recipients to a minimal set?
• Should we replace native Agent alerts with Extended Events and custom notification logic to gain control over noise and permission scope?