Azure Monitor vs Azure SQL Database: Dynamic Threshold Support Across All Metrics?

Goal

Reduce alert noise while preserving operational visibility for Azure SQL Database workloads.

Context

Azure Monitor offers static and dynamic threshold alert rules for some SQL Database metrics such as CPU percentage and DTU usage. Dynamic thresholds adapt to historical patterns, but only a subset of metrics expose this feature. Suppression rules can silence notifications during maintenance windows or after a set number of consecutive triggers, yet suppression is not universally available across all metric types.

Unresolved Decision

When a metric lacks dynamic threshold support, should we rely on static thresholds combined with suppression, or is there a way to enable dynamic behavior across all metrics without creating excessive rules and incurring higher costs?

Questions

• Which Azure SQL Database metrics currently support dynamic threshold alerts?
• Can suppression rules be applied to metrics that do not expose dynamic thresholds, and if so, how are they enforced?
• What is the most cost‑effective strategy to minimize noise for metrics that only support static thresholds?