The Overview tab on the query details view displays five sections containing information about the selected query. The sections and the metrics each displays are shown as following.
Query Information
| Metric | Description | Type |
|---|---|---|
| Query ID | System-wide unique ID that identifies the query | String |
| Proc ID | ID of the parsing engine that runs the query | String |
| Start time | The time the query was submitted | Number |
| Statement type | SQL statement type the query used | String |
| Row count | Number of result rows returned by the query | Number |
| Active AMPs | Number of AMPs involved in executing the query | Number |
| Step count | Number of steps in the query plan | Number |
| Cache flag | The cache flag types are:
|
String |
Query Duration
| Metric | Description | Type |
|---|---|---|
| Time active | Number of seconds the query spent running. Excludes any time the query was delayed before being executed. | Number |
| Time delay | Number of seconds the query was delayed before running | Number |
| Total duration | Total elapsed time it took for the query to run once it was submitted | Number |
Query Performance
| Metric | Description | Type |
|---|---|---|
| AMP CPU time | Total number of CPU seconds consumed by AMPs in processing the query | Number |
| Parser CPU time | Total number of CPU seconds consumed by the parsing engine in processing the query | Number |
| Total I/O count | Total number of I/O requests the query used | Number |
| Impact CPU | Impact of jobs on the system taking CPU skew into account. The value is equal to the sum of the highest CPU time in seconds consumed by any one AMP on behalf of a job or query multiplied by the number of AMPs. | Number |
| CPU skew | CPU skew for the entire query | Percent |
| I/O skew | I/O skew for the entire query | Percent |
| PJI | Ratio of the CPU milliseconds per I/O for the query, where a larger Product Join Index number indicates system performance degradation | Number |
| Unnecessary I/O | All AMP I/O divided by all AMP CPU, displayed in milliseconds, to reveal large amounts of I/O occurring over a short period of time | Number |
| Spool usage | Amount of spool consumed by the query | Number |
| Gating efficiency | Percentage indicating the percentage of the overall query duration spent executing versus being delayed. A value of 100 indicates all time was spent executing. | Percent |
| Burn rate | Percentage of the overall system capacity effectively consumed by the query during its execution | Percent |
| Time expansion | Ratio of how long the query took to run versus how long it could have ideally run. The larger the number, the more the run time of the query was expanded. For example, a value of 8.8 means an expansion of 8.8 times the ideal execution time. | Number |
Workload Information
| Metric | Description | Type |
|---|---|---|
| Starting workload | Name of the workload under which the query started execution | String |
| Final workload | Name of the workload under which the query finished | String |
Session Information
| Metric | Description | Type |
|---|---|---|
| Username | Name of the user who submitted the query | String |
| Application | Name of the application that submitted the query | String |
| Version | Version of the application that submitted the query | String |
| Account | Account of the user who submitted the query | String |
| App ID | The ID of the application used to access the Analytics Database. Typically the App ID is the name and version of the Teradata Tool or Utility accessing Analytics Database. | String |
| Client ID | ID of the client that submitted the query | String |
| Client address | IP address of the client | String |