WARNING: I do NOT currently recommend enabling the Automatic Plan Correction feature due to issues described in my post, Automatic Plan Correction Could be a Great Auto Tuning Feature for SQL Server. Here’s why it Isn’t.
Grab a pen and notepad, and jot down your answers as you go, then check your answers at the key at the bottom of the page.
Questions
Q1. Automatic Plan Correction works at the…
- Instance level
- Object level
- Database level
- Schema level
Q2. You can use the ‘Queries with High Variation Query Store Report’ in Standard Edition.
- True
- False
Q3. You can see suggestions in sys.dm_db_tuning_recommendations in Standard Edition.
- True
- False
Q4. You can see suggestions in sys.sys.dm_db_tuning_recommendations in Enterprise Edition if you have Query Store Enabled, but do not SET AUTOMATIC_TUNING (FORCE_LAST_GOOD_PLAN = ON).
- True
- False
Q5. Can you manually un-force a query plan that has been forced with Automatic Plan Correction?
- No, you cannot un-force it
- Yes, but it may be auto-tuned again in the future
- Yes, and it will never be auto-tuned again in the future
Q6. Automatic Plan Correction may force a plan for a query with a recompile hint.
- True
- False
Q7. You may manually force a plan in Query Store for a query with a recompile hint.
- True
- False
Scroll down for the answer key :point_down:
Answer Key
- A1: Database level
- A2: True
- A3: False
- A4: True
- A5: Yes, but it may be auto-tuned again in the future
- A6: False
- A7: True
REGISTER