| title | Display and Save Execution Plans | Microsoft Docs | ||||||
|---|---|---|---|---|---|---|---|
| ms.custom | |||||||
| ms.date | 08/21/2017 | ||||||
| ms.prod | sql | ||||||
| ms.prod_service | database-engine, sql-database | ||||||
| ms.reviewer | |||||||
| ms.technology | performance | ||||||
| ms.topic | conceptual | ||||||
| helpviewer_keywords |
|
||||||
| ms.assetid | bcd6f094-c613-4835-ae19-4caaadb4bb17 | ||||||
| author | julieMSFT | ||||||
| ms.author | jrasnick | ||||||
| monikerRange | =azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current |
[!INCLUDEappliesto-ss-asdb-xxxx-xxx-md] This section explains how to display execution plans and how to save execution plans to a file in XML format by using Microsoft [!INCLUDEssManStudioFull].
Execution plans graphically display the data retrieval methods chosen by the [!INCLUDEssNoVersion] Query Optimizer. Execution plans represent the execution cost of specific statements and queries in [!INCLUDEssNoVersion] using icons rather than the tabular representation produced by the SET SHOWPLAN_ALL or SET SHOWPLAN_TEXT statements. This graphical approach is useful for understanding the performance characteristics of a query.
While the [!INCLUDEssNoVersion] Query Optimizer produces only one execution plan, there is the concept of estimated execution plan and actual execution plan.
- An estimated execution plan returns the execution plan as produced by the Query Optimizer at compile time. Producing the estimated execution plan does not actually execute the query or batch, and therefore does not contain any runtime information, such as actual resource usage metrics or runtime warnings.
- An actual execution plan returns the execution plan as produced by the Query Optimizer, and after queries or batches finish execution. This includes runtime information about resource usage metrics and any runtime warnings.
For more information on query execution plans, see the Query Processing Architecture Guide.