DP-300 · Question #207
MyDB1 is an Azure SQL on Azure virtual machine (VM) database. You identify a long-running query. You want to determine where the operation in the query is causing performance problems. You need to…
The correct answer is B. Display an actual execution plan. To identify performance bottlenecks in a long-running query using runtime information in SSMS, you should display the actual execution plan.
Question
Options
- AAnalyze an actual execution plan.
- BDisplay an actual execution plan.
- CDisplay an estimated execution plan.
- DCompare execution plans.
How the community answered
(37 responses)- A5% (2)
- B84% (31)
- C8% (3)
- D3% (1)
Why each option
To identify performance bottlenecks in a long-running query using runtime information in SSMS, you should display the actual execution plan.
While analysis is performed on an actual execution plan, 'Analyze an actual execution plan' is not the specific SSMS command to generate it; the action is 'Display' or 'Include actual execution plan'.
The 'Display an actual execution plan' feature in SQL Server Management Studio (SSMS) executes the query and then provides detailed runtime statistics, including actual rows, I/O, and CPU usage for each operator, which is essential for diagnosing real-time performance issues and trying query variations.
An estimated execution plan is generated without running the query and therefore does not contain runtime information necessary to diagnose actual performance problems.
Comparing execution plans is a subsequent step, used after generating at least two plans, rather than the initial action to obtain the runtime performance data.
Concept tested: SQL Server Management Studio (SSMS) actual execution plans
Source: https://learn.microsoft.com/en-us/sql/relational-databases/performance/display-an-actual-execution-plan?view=sql-server-ver16
Community Discussion
No community discussion yet for this question.