Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft DP-300 Exam - Topic 1 Question 127 Discussion

SIMULATIONTask 8You plan to perform performance testing of db1.You need prevent db1 from reverting to the last known good query plan.
A) See the explanation part for the complete Solution

Microsoft DP-300 Exam - Topic 1 Question 127 Discussion

Actual exam question for Microsoft's DP-300 exam
Question #: 127
Topic #: 1
[All DP-300 Questions]

SIMULATION

Task 8

You plan to perform performance testing of db1.

You need prevent db1 from reverting to the last known good query plan.

Show Suggested Answer Hide Answer
Suggested Answer: A

To prevent db1 from reverting to the last known good query plan, you need to disable the automatic plan correction feature for the database.This feature is enabled by default and allows the Query Store to detect and fix plan performance regressions by forcing the last good plan1.However, if you want to test the performance of different plans without interference from the Query Store, you can turn off this feature by using the ALTER DATABASE SCOPED CONFIGURATION statement2.

Here are the steps to disable the automatic plan correction feature for db1:

Connect to db1 using SQL Server Management Studio, Azure Data Studio, or any other tool that supports Transact-SQL statements.

Open a new query window and run the following command:ALTER DATABASE SCOPED CONFIGURATION SET AUTOMATIC_TUNING (FORCE_LAST_GOOD_PLAN = OFF); GO

This command will disable the automatic plan correction feature for db1 and allow the Query Optimizer to choose the best plan based on the current statistics and parameters3.

To verify that the automatic plan correction feature is disabled for db1, you can query the sys.database_scoped_configurations catalog view. The value of the force_last_good_plan column should be 0 for db1.

These are the steps to disable the automatic plan correction feature for db1.


Contribute your Thoughts:

0/2000 characters
Vernell
4 days ago
I feel like it’s a common issue in testing.
upvoted 0 times
...
Kirby
9 days ago
It prevents reverting to old plans.
upvoted 0 times
...
Virgina
14 days ago
Why do you say that?
upvoted 0 times
...
Kirby
20 days ago
I think option A is the best choice.
upvoted 0 times
...
Rex
25 days ago
This question is tricky.
upvoted 0 times
...
Corrinne
30 days ago
I feel like it’s about stability.
upvoted 0 times
...
Tammara
1 month ago
It prevents reverting to old plans.
upvoted 0 times
...
Shelia
1 month ago
Why do you think that?
upvoted 0 times
...
Tammara
2 months ago
I think option A is the best choice.
upvoted 0 times
...
Keneth
2 months ago
Agreed, it’s confusing.
upvoted 0 times
...
Shay
2 months ago
This question is tricky.
upvoted 0 times
...
Annmarie
2 months ago
This is a common practice, nothing surprising here!
upvoted 0 times
...
Nu
2 months ago
I heard this can lead to performance issues if not monitored.
upvoted 0 times
...
Dorathy
2 months ago
Wait, are we sure this won't mess up other queries?
upvoted 0 times
...
Annmarie
4 months ago
Totally agree, that's the way to go!
upvoted 0 times
...
Julene
4 months ago
Just set the plan stability option to prevent reversion.
upvoted 0 times
...
Johana
5 months ago
I feel like there was a specific command we discussed that prevents the plan from being cached, but I can't remember the details right now.
upvoted 0 times
...
Shawnna
5 months ago
This question seems similar to one we practiced on query optimization; I think we might have to change the database settings.
upvoted 0 times
...
Ming
5 months ago
I remember something about using `sp_recompile` to force a recompilation, but I can't recall if that's the right approach here.
upvoted 0 times
...
Elouise
5 months ago
I think we need to use the `OPTION (RECOMPILE)` hint to avoid reverting to the last good plan, but I'm not entirely sure.
upvoted 0 times
...

Save Cancel