ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Enable Azure SQL Database automatic tuning only after confirming Query Store is read-write and actual_state matches desired_state; otherwise plan correction may be silently inactive.
Azure SQL Database Automatic Tuning can shift query execution plans automatically. This post walks through the three modes, when Parameter Sensitive Plans help, and how to inspect and control plan changes with T-SQL.
Azure SQL Database’s Automatic Tuning can create or drop indexes and force last‑good plans, reducing manual tuning effort. Learn how to enable it, inspect applied actions, and understand its trade‑offs in this practical guide.
Automatic Tuning in Azure SQL Database lets the engine detect and fix regressions with minimal DBA effort. Learn how to enable, verify, and monitor the feature, plus key trade‑offs and a practical example.
Automatic Tuning enabled but no performance gains? Diagnose Query Store state, per-option settings, and the recommendation lifecycle in sys.dm_db_tuning_recommendations to find why nothing is being applied.
Azure SQL Database can detect plan regressions and force the last known good plan automatically. Here’s how FORCE_LAST_GOOD_PLAN works, how to audit it, and where it falls short.
Identify and resolve Azure SQL Database plan regression using Automatic Tuning Plan Correction with a step‑by‑step diagnostic guide.
Azure SQL Database can detect plan regressions via Query Store and automatically force the last good plan. Here's how FORCE_LAST_GOOD_PLAN works, how to inspect it, and where it falls short.
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. Do
azuresqldatabase