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 Exam DP-300 Topic 1 Question 115 Discussion

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

You have an Azure SQL database.

You discover that the plan cache is full of compiled plans that were used only once.

You run the select * from sys.database_scoped_configurations Transact-SQL command and receive the results shown in the following table.

You need relieve the memory pressure.

What should you configure?

Show Suggested Answer Hide Answer
Suggested Answer: C

OPTIMIZE_FOR_AD_HOC_WORKLOADS = { ON | OFF }

Enables or disables a compiled plan stub to be stored in cache when a batch is compiled for the first time. The default is OFF. Once the database scoped configuration OPTIMIZE_FOR_AD_HOC_WORKLOADS is enabled for a database, a compiled plan stub will be stored in cache when a batch is compiled for the first time. Plan stubs have a smaller memory footprint compared to the size of the full compiled plan.

Incorrect Answers:

A: LEGACY_CARDINALITY_ESTIMATION = { ON | OFF | PRIMARY }

Enables you to set the query optimizer cardinality estimation model to the SQL Server 2012 and earlier version independent of the compatibility level of the database. The default is OFF, which sets the query optimizer cardinality estimation model based on the compatibility level of the database.

B: QUERY_OPTIMIZER_HOTFIXES = { ON | OFF | PRIMARY }

Enables or disables query optimization hotfixes regardless of the compatibility level of the database. The default is OFF, which disables query optimization hotfixes that were released after the highest available compatibility level was introduced for a specific version (post-RTM).


https://docs.microsoft.com/en-us/sql/t-sql/statements/alter-database-scoped-configuration-transact-sql

Contribute your Thoughts:

James
9 days ago
I'm going with C) OPTIMIZE_FOR_AD_HOC_WORKLOADS. It's the only one that actually makes sense in the context of the problem. The others just seem like random database knobs to twiddle.
upvoted 0 times
...
Chantell
10 days ago
Haha, I love how these options are like a mix of real and made-up sounding things. 'LEGACY_CARDINALITY_ESTIMATION' - sounds like something straight out of a Dilbert comic!
upvoted 0 times
...
Wava
11 days ago
Hmm, I'm not sure about that. What if we try D) ACCELERATED_PLAN_FORCING? It might help us get those plans out of the cache a bit faster.
upvoted 0 times
Shoshana
4 hours ago
User1: I think D) ACCELERATED_PLAN_FORCING could work.
upvoted 0 times
...
...
Willard
27 days ago
I'm not sure, but I think LEGACY_CARDINALITY_ESTIMATION could also help in this situation.
upvoted 0 times
...
Merrilee
29 days ago
I agree with Lizette. It seems like the best option to relieve memory pressure.
upvoted 0 times
...
Lizette
2 months ago
I think we should configure QUERY_OPTIMIZER_HOTFIXES.
upvoted 0 times
...
Vinnie
2 months ago
I think C) OPTIMIZE_FOR_AD_HOC_WORKLOADS is the way to go. It's the only option that directly addresses the issue of the plan cache being full of one-time plans.
upvoted 0 times
Theodora
21 days ago
User4: Let's configure OPTIMIZE_FOR_AD_HOC_WORKLOADS then.
upvoted 0 times
...
Ruthann
22 days ago
User3: I agree, we need to relieve the memory pressure.
upvoted 0 times
...
Sharmaine
1 months ago
User2: Yeah, that option directly addresses the issue of the plan cache being full of one-time plans.
upvoted 0 times
...
Yun
1 months ago
User1: I think C) OPTIMIZE_FOR_AD_HOC_WORKLOADS is the way to go.
upvoted 0 times
...
...

Save Cancel