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.
Query Store turns SQL Server plan regressions from guesswork into evidence. Learn how to enable it, capture query history, force a known-good plan, and avoid the storage and replica traps.
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.
When a SQL Server query suddenly slows down without code changes, Query Store captures execution plans over time so you can compare them and force a known-good plan back into service.
Learn how to use SQL Server Query Store to capture execution history, compare plans across deployments, and force a stable plan when the optimizer picks a bad one.
A practical guide to enabling Azure SQL Database Query Store, querying execution metrics via DMVs, detecting plan regressions, and managing retention and overhead.
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.
Enable SQL Server Query Store with a production-ready configuration, learn to spot plan regressions using catalog views, force plans safely, and avoid the common mistakes that silently disable capture or cause forced-plan regressions.
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.
microsoftsqlserver
azuresqldatabase