Execution Plan Summary

Displays a useful summary of the selected execution plan. Linked from the Activity | Session Detail report, as well as several other reports throughout SQL CoPilot. The report is divided into several sections.

Summary Information and Charts

A summary of the plan and two charts for quickly identifying the most expensive statements, and the tables with the highest estimated I/O cost.

What It ShowsComments
Plan Handle
Number of OperatorsThe number of nodes you see when you look at the graphical plan. This is a good indication of complexity.
Estimated I/O CostThe total estimated I/O cost of all operators
Estimated CPU CostThe total estimated CPU cost of all operators
Is ParallelThe estimated plan has parallel operations. This does not mean that the actual plan uses parallelism, but it is likely
Missing IndexesThe number of potential missing indexes identified by SQL Server. The index details are displayed further down in this report
WarningsThe number of warnings generated by SQL Server. The details are displayed further down at the bottom of this report


A list of all statements in the execution plan. A multi-statement query or stored procedure generates a separate plan for each statement - all with the same plan handle. Each row can be expanded for more information.

What It ShowsComments
Statement IdIdentifies the order of statements in the plan and the source SQL
TypeNormally one of SELECT, INSERT, UPDATE, DELETE, but there are several others
Optimization LevelFULL = A query complex enough that it needed compiling into a plan.
TRIVIAL = A straightforward query that didn't need to be compiled
Early Abort ReasonIf this is not blank it indicates the reason why SQL Server stopped generation a plan and used what was generated so far.
You want to see GoodEnoughPlanFound. For complex plans this may show Timeout, which indicates that SQL Server may have run with a sub-optimal plan. This can be caused by overly complex SQL, or indicate that the server was under very heavy load at the time
Estimated CostThe figure you get in the graphical plan when you hover the mouse over the root node. It should be treated as an approximation, and does not necessarily represent what happened when the plan was actually executed
Percentage CostThe estimated cost as a percentage of the total for all statements
Estimated RowsThe estimated number of rows returned or processed by the statement
Creation TimeThe time this plan was first compiled
Last Execution TimeThe time this plan was last executed
Execution CountThe number of times this plan has been executed
Last CPU Time (ms)The number of milliseconds of worker time that were used when this was last executed
Last Logical ReadsThe number of logical reads from the last execution
Last Physical ReadsThe number of physical reads from the last execution
Last Logical WritesThe number of logical writes from the last execution
Last Elapsed Time (ms)The number of milliseconds this statement took to run when it was last executed
Plan GenerationA value other than 1 here indicates that recompiles are occurring. This may be caused by a number of reasons, including use of temporary tables in which statistics are updated during execution, and DDL statements interspersed with DML
Compiled ParamsIf this is not blank it shows the values used for each parameter when the statement was last compiled. Particularly useful if you suspect parameter sniffing may be causing some queries to go slow.
SQLThe SQL for the statement


All tables touched by the execution plan. Each row can be expanded for more information.

What It ShowsComments
Database, Schema and TableIdentifies the table in question. Table variables are displayed with blank database and schema
Estimated Data (bytes)The number of rows in total that are read from, inserted, updated or deleted
Estimated I/O CostThe sum of all estimated I/O cost figures across all operations on the table
Percentage I/O CostThe estimated I/O cost as a percentage of the total for all tables
Summary of operationsWhen the row is expanded this shows the operations (such as scan or seek) that are performed with a breakdown of I/O cost, the indexes (N/A if a table scan on a heap), and the columns involved in the seeks or scans

Missing Indexes

If SQL Server has suggested any missing indexes in the plan, these are displayed here.


If SQL Server has generated any warnings in the plan, these are displayed here.

< Activity | Session Detail Activity | Current | Locks >