HOTSPOT
You are reviewing the execution plans in the query plan cache. You observe the following:
– There are a large number of single use plans.
– There are a large number of simple execution plans that use multiple CPU cores.
You need to configure the server to optimize query plan execution.
Which two setting should you modify on the properties page for the Microsoft SQL Server instance? To answer,
select the appropriate settings in the answer area.
Hot Area:

Answer:

Explanation:
* Optimize for ad hoc workloads
The optimize for ad hoc workloads option is used to improve the efficiency of the plan cache for workloads that
contain many single use ad hoc batches. When this option is set to 1, the Database Engine stores a small
compiled plan stub in the plan cache when a batch is compiled for the first time, instead of the full compiled
plan. This helps to relieve memory pressure by not allowing the plan cache to become filled with compiled plans
that are not reused.
* Cost Threshold for Parallelism
Use the cost threshold for parallelism option to specify the threshold at which Microsoft SQL Server creates and
runs parallel plans for queries. SQL Server creates and runs a parallel plan for a query only when the estimatedcost to run a serial plan for the same query is higher than the value set in cost threshold for parallelism. The
cost refers to an estimated elapsed time in seconds required to run the serial plan on a specific hardware
configuration.
5 means 5 seconds, but is is 5 seconds on a machine internal to Microsoft from some time in the 1990s.
There’s no way to relate it to execution time on your current machine, so we treat it as a pure number now.
Raising it to 50 is a common suggestion nowadays, so that more of your simpler queries run on a single thread.