This is the multi-page printable view of this section. Click here to print.
After you profile a specific query, the Management Console Explain page displays profile data like query duration, projection metadata, execution events, optimizer events, and metrics in a pie chart.
See the following links for more information on the kinds of profile data you can review on the Management Console Explain page:
To view projection metadata for a specific projection, click the projection name in the EXPLAIN output. Metadata for that projection opens in a pop-up window.
To view projection data for all projections accessed by that query, click the View Projection Metadata button at the top of the Explain page. The metadata for all projections opens in a new browser window.
The projection metadata includes the following information:
Projection ID
Schema name
Whether or not it is a superprojection
Sort columns
IDs of the nodes the projection is stored on
Whether or not it is segmented
Whether or not it is up to date
Whether or not it has statistics
Owner name
Anchor table name
To display a SQL script that can recreate the projection on a different cluster, click Click to get export data. This script is identical to the output of the EXPORT_OBJECTS function. The SQL script opens in a pop-up window.
Copy and paste the command from this window, and click Close.
This pie chart appears in the upper-right corner of the Query Plan window. It shows what percentage of total query processing was spent in each phase of processing the query.
The phases included in the pie chart (when applicable) are:
Plan
InitPlan
SerializePlan
PopulateVirtualProjection
PreparePlan
CompilePlan
ExecutePlan
AbandonPlan
Hover over the slices on the pie chart or over the names of the phases in the box to get additional information. You can see the approximate number of milliseconds (ms) and percentage used during each phase.
In the Path Information view, the area to the right of each query path contains profile metrics for that path.
Disk—Bytes of data accessed from disk by each query path. If none of the query paths accessed the disk data, all the values are 0.
Memory—Bytes of data accessed from memory by each query path.
Sent—Bytes of data sent across the cluster by each query path.
Received—Bytes of data received across the cluster by each query path.
Time—Number of milliseconds (ms) that the query path took to process on a given node, shown on progress bars. The sum of this data does not match the total time required to execute the query. This mismatch occurs because many tasks are executed in parallel on different nodes.
Hover over the progress bars to get more information, such as total bytes and percentages.
To help you monitor your database system, Vertica logs significant events that affect database performance and functionality. Click View Execution Events to see information about the events that took place while the query was executing.
If the View Execution Events button is not enabled, click Profile to retrieve the profile data, including the execution events.
The arrows on the header of each column allow you to sort the table in ascending or descending order of that column.
The execution events are described in the following table.
| Event Characteristic | Details |
| Time | Clock time when the event took place. |
| Node Name | Name of the node for which information is listed. |
| Session ID | Identifier of the session for which profile information is captured. |
| User ID | Identifier of the user who initiated the query. |
| Request ID | Unique identifier of the query request in the user session. |
| Event Type | Type of event processed by the execution engine. For a list of events and their descriptions, see Initial process for improving query performance. |
| Event Description | Generic description of the event. |
| Operator Name |
Name of the Execution Engine component that generated the event. Examples include but are not limited to:
Values from the Operator name and Path ID columns let you tie a query event back to a particular operator in the query plan. If the event did not come from a specific operator, then this column is NULL. |
| Path ID | Unique identifier that Vertica assigns to a query operation or a path in a query plan. If the event did not come from a specific operator, this column is NULL. |
| Event OID | A unique ID that identifies the specific event. |
| Event Details | A brief description of the event and details pertinent to the specific situation. |
| Suggested Action | Recommended actions (if any) to improve query processing. |
To help you monitor your database system, Vertica logs significant events that affect database performance and functionality.Click View Optimizer Events to see a table of the events that took place while the optimizer was planning the query.
If the View Optimizer Events button is not enabled, click Profile to retrieve the profile data, including the optimizer events.
The arrows on the header of each column allow you to sort the table in ascending or descending order of that column.
The following types of optimizer events may appear in the table:
| Event characteristic | Details |
| Time | Clock time when the event took place. |
| Node Name | Name of the node for which information is listed. |
| Session ID | Identifier of the session for which profile information is captured. |
| User ID | Identifier of the user who initiated the query. |
| Request ID | Unique identifier of the query request in the user session. |
| Event Type | Type of event processed by the optimizer. |
| Event Description | Generic description of the event. |
| Event OID | A unique ID that identifies the specific event. |
| Event Details | A brief description of the event and details pertinent to the specific situation. |
| Suggested Action | Recommended actions (if any) to improve query processing. |