Execution Plan Query Attributes in the Details Panel

The following table lists attributes that can appear in the Details Panel when the overall query (request) is highlighted in the Tree Panel. This panel is displayed at the bottom right of the Studio Modeler pane when you click Show Execution Plan, or of the Studio Manager pane when you click Show Query Plan.

These attributes can also be found in the logged execution plan, although some of them are estimates before execution and actual run-time values after execution.

Field	Description
Background data source read time	Time spent by background threads in all FETCH and PROCEDURE nodes in the execution plan.
Background server processing time	Time spent by background threads in all the nodes (except for FETCH and PROCEDURE) in the execution plan.
Data ship data transfer time	Time required to transfer data from one data source to another.
Elapsed execution time	Amount of wall-clock time that the server used to execute the query. This time is the total of Query initialization time, Foreground server processing time, and Foreground data source read time.
Foreground server processing time	Fraction of the Elapsed execution time that the server used in the actual execution of the query; that is, the processing time of the nodes in the execution plan. This time does not include the time used to read rows from the data sources. By comparing this time with Foreground data source read time, you can determine how much time was spent by the server versus the time spent in the data sources.
Peak memory reserved	Peak memory reserved for current request.
Query initialization time	Time the server used to analyze the query, create and optimize an execution plan, rewrite the query, and establish connections (from the pool if pooling is configured) to the data sources. If data ship is involved, time is spent creating a data ship temp table at the data ship target, and shipping the data. With multiple data shipments to multiple temp tables, these tasks are done in parallel by separate threads, and the shipped segment that takes the longest keeps the query initialization time clock running.
Reset count
Resolved SQL	Fully resolved SQL text.
Rows modified	Number of rows modified by the request.
Rows returned	Number of rows produced by an execution node. If you want to know how many rows were read by the node, look at the returned row counts of the node’s children.
Server version	Version of the server software.
Speed up due to concurrency	Estimate of how much faster the query ran because of threading. For example, 100% means the query ran twice as fast with threading.
Submitted SQL	Original SQL text.