Execution Plan Node Attributes in the Details Panel
The following table lists attributes that can appear in the Details 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. When you select a node in the Tree Panel on the left, its attributes are displayed.
The following table lists attributes that can appear in the Details Panel when a node 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.
Note: See Execution Plan Nodes in the Tree Panel, for a list of nodes.
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 |
|
Name of the algorithm used by the node; for example HASH JOIN or SORT/MERGE JOIN. |
|
|
More details about the algorithm used. |
|
|
For SCAN or PROCEDURE: how much time the child thread spent on reading from the data source. |
|
|
For nodes other than SCAN, PROCEDURE, INSERT, UPDATE, DELETE, or MERGE: time spent processing this node by a background thread. This time is zero if the node was processed by a foreground thread. |
|
|
For SCAN. |
|
|
For SELECT. |
|
|
For SCAN. |
|
|
Shows the criteria used by a JOIN, FILTER, GROUP BY, or ORDER BY node. Condition or predicate applied during an operation |
|
|
For SCAN or SELECT. A report of the estimated number of rows to be shipped, and the amount of time consumed to get the cost estimate. When a condition blocks the use of data ship, this field usually describes the condition, case, or option that blocked optimization. |
|
|
For SCAN. |
|
|
For SCAN. Shows where the results of SQL execution will be sent. The presence of Data ship target indicates that data ship will be performed. |
|
|
For SCAN. |
|
|
For SCAN or PROCEDURE. |
|
|
For SCAN or PROCEDURE. |
|
|
For SCAN or PROCEDURE. |
|
|
For INSERT, UPDATE, DELETE or MERGE. |
|
|
Estimated cardinality for the left input in a binary join. Pre-execution (Show Execution Plan button) Details Panel only |
|
|
Estimated cardinality for the right input in a binary join. Pre-execution (Show Execution Plan button) Details Panel only |
|
|
Pre-execution (Show Execution Plan button) Details Panel only. Logged execution plan records actual Rows Returned. |
|
|
If the operation for the node is still running, status can be PARTIAL RESULTS or NOT EXECUTED. |
|
|
For SELECT. |
|
|
For SCAN or PROCEDURE. Fraction of the Elapsed execution time that the main thread used to read data from the data sources. By comparing this time with Foreground server processing time, you can determine how much time was spent by the server vs. the time spent in the data sources. |
|
|
For nodes other than SCAN, PROCEDURE, INSERT, UPDATE, DELETE, or MERGE: fraction of the elapsed time used by the node. This time is zero if the node was processed by a background thread. |
|
|
|
|
|
Why the node was not pushed to the data source. |
|
|
For SELECT. |
|
|
Peak memory reserved for current node. |
|
|
Peak memory used for current node. |
|
|
For PROCEDURE. |
|
|
For PROCEDURE. |
|
|
Set of output columns in a SELECT node. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For SCAN. |
|
|
For SCAN. |
|
|
SQL text executed by the node. In a FETCH or PROCEDURE node, this field contains the actual data-source-specific query that was pushed. |
|
|
For SELECT. |