| Account |
Account of the user who submitted the query |
String |
| Active AMPs |
Number of AMPs involved in executing the query |
Number |
| AMP CPU Time |
Total number of CPU seconds consumed by AMPs in processing the query |
Number |
| 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 |
| Burn Rate |
Percentage of the overall system capacity effectively consumed by the query during its execution |
Percent |
| Cache Flag |
The cache flag types are:- T: The flag is found in step cache
- S: The query is a parameterized query and a specific plan is generated.
- G: The query is a parameterized query and a generic plan is generated.
- A: The query is a parameterized query and a specific always decision is taken. Each time a query is submitted, the USING values are considered and the query is parsed.
|
String |
| Client Address |
IP address of the client |
String |
| Client ID |
ID of the client that submitted the query |
String |
| CPU Skew |
CPU skew of the entire query |
Percent |
| Error Code |
Error code associated with the query |
String |
| Final Workload |
Name of the workload under which the query finished |
String |
| Flagged |
Denotes whether the query has been flagged for further analysis |
String |
| Gating Efficiency |
The percentage of the overall query duration spent executing versus being delayed. A value of 100 indicates that all time was spent executing. |
Percent |
| Impact CPU |
Impact of jobs on the system taking CPU skew into account. The value is equal to 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 |
| I/O Skew |
I/O skew of the entire query |
Percent |
| Max AMP CPU Time |
The maximum CPU consumed by a single AMP while executing the query |
Number |
| Max AMP I/O |
The maximum IOs submitted by a single AMP while executing the query |
Number |
| Parser CPU Time |
Total amount of CPU seconds consumed by the parsing engine in processing the query |
Number |
| PJI |
Ratio of the CPU milliseconds per I/O for the query, where a larger Product Join Index number indicates system performance degradation |
Number |
| Proc ID |
ID of the parsing engine that run the query |
String |
| Query ID |
System-wide unique ID that identifies the query |
String |
| Row Count |
Number of result rows returned by the query |
Number |
| Spool Usage |
Amount of spool consumed by the query, using a 1024 byte kilobyte as the base |
Number |
| Start Time |
The time the query was submitted |
Number |
| Starting Workload |
Name of the workload under which the query started execution |
String |
| Statement Type |
SQL statement type the query used |
String |
| Step Count |
Number of steps in the query plan |
Number |
| 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 |
| 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 execution 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 |
| Total I/O Count |
Total number of I/O requests the query used |
Number |
| Unnecessary I/O |
All AMP I/O divided by all AMP CPU, displayed in milliseconds, to reveal large amounts of I/O occurring in proportion to the CPU consumed |
Number |
| Username |
Name of the user who submitted the query |
String |