Skip to content

Commit 13bd6e4

Browse files
committed
update
1 parent 8e47797 commit 13bd6e4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

learn-pr/wwl-data-ai/configure-databases-for-optimal-performance/includes/4-describe-automatic-tuning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ In the example above, you can see a check mark on **Plan ID 1**, which means tha
2020

2121
The plan will revert back to the last known good plan after 15 executions of the query.
2222

23-
When plan forcing occurs automatically, the database engine applies the last known good plan and will also continue to monitor query execution plan performance. If the forced plan doesn't perform better than the previous plan, it is then unforced and force a new plan to be compiled. If the forced plan continues to outperform the previously bad plan, it remains forced until such time as a recompile occurs.
23+
When plan forcing happens automatically, the database engine applies the last known good plan and keeps an eye on query execution performance. If the forced plan doesn't perform better than the previous one, it's unforced, and a new plan is compiled. However, if the forced plan continues to outperform the previous bad plan, it stays in place until a recompile occurs.
2424

2525
You can enable automatic plan correction via a T-SQL query. The Query Store must be enabled and must be in Read-Write mode for the command to succeed. If either of those two criteria aren't met, the ALTER statement fails.
2626

0 commit comments

Comments
 (0)