Automatic Tuning default disabled in new Azure SQL Databases
0 reputation · 07 Sept 2024, 17:25 UTC
Goal
Determine the default enablement state of Automatic Tuning for newly created Azure SQL Databases and clarify the current decision around this setting.
Context
Automatic Tuning offers auto‑index optimization, auto‑repair of query plans, and automatic statistics rebuilds. Elastic pools support the feature, but each database must toggle it individually. Documentation states that new databases are created with Automatic Tuning disabled, requiring explicit enablement by the administrator.
Uncertainty
It is not documented whether Microsoft plans to change the default to enabled in future releases, nor is there a pool‑wide toggle that could simplify deployment. Additionally, enabling the feature can temporarily increase resource consumption during index rebuilds, but its effect on overall cost remains unclear.
Questions
- Will Microsoft enable Automatic Tuning by default for new Azure SQL Databases in upcoming releases?
- How does enabling Automatic Tuning in an elastic pool affect resource usage and billing compared to individual databases?
- What mitigations are recommended to prevent transient performance regressions when Automatic Tuning is turned on?
