Metrics for a Teradata system that display in the Viewpoint Dashboard Queries view are listed following.
| Metric | Description | Type |
|---|---|---|
| Account | Account from which a query was submitted | String |
| Blocked Time | How long the query has been blocked | Number |
| CPU Skew | Percentage of how inefficiently a query or job was executed in terms of CPU parallelism. A value of 0% indicates the query was executed perfectly in parallel, meaning each AMP consumed identical amounts of CPU. A value of 50% indicates a single AMP consumed twice as much CPU as the average. As CPU Skew approaches 100%, it indicates the query or job was not executed in parallel. | Percent |
| CPU Use | Percent of available CPU seconds on the system used during the last sampling period | Percent |
| Delay Time | Duration of time request has been delayed by utility, system throttle, workload throttle, or workload group throttle rules | Number |
| Delayed By | Names of the throttles causing the query to be delayed | String |
| Δ CPU | Total CPU usage time consumed, in seconds, since the last sample | Number |
| Δ I/O | I/O count since the last sample | Number |
| Duration | How long the query has been running | Number |
| Host | Host ID or LAN ID associated with the PE that processed the login request for the session | Number |
| Impact CPU | CPU impact on the system based on the highest utilized AMP. (Teradata Database 15.0 and earlier) Calculated at the snapshot level. (Teradata Database 15.10 and later) Calculated at the request level. | Number |
| In State | How long the query has been in the current state | Number |
| Partition | Partition in which the query is running | String |
| PJI | Ratio of the CPU milliseconds per I/O for the query, where a larger Product Join Index number indicates system performance degradation | Number |
| Proxy Username | (Teradata Database 15.0 and later) Name of the proxy user when a trusted session is used | String |
| Query Band | Entire query band string. Query bands are a set of name-value pairs defined by the user to tag sessions or transactions with an ID through a SQL interface. | String |
| Req CPU | CPU seconds needed to run the query | Number |
| Req CPU Skew | (Teradata Database 15.10 and later) CPU skew for the current query | Percent |
| Req Count | Number of queries the session has executed | Number |
| Req I/O | Disk I/Os performed to run the query | Number |
| Req I/O Skew | (Teradata Database 15.10 and later) I/O skew for the current query | Percent |
| Session ID | Unique session identifier | Number |
| Snapshot CPU Skew | CPU skew during the last sample | Percent |
| Snapshot I/O Skew | I/O skew during the last sample | Percent |
| Spool | Spool space the query requires, using a 1024 byte kilobyte as the base | Number |
| Start | Time that the query started running on Analytics Database | Number |
| State | Text describing the current state of the query | String |
| State Icon | Icon representing the current state of the query | Icon |
| Temp Space | Temp space used by the query, using a 1024 byte kilobyte as the base | Number |
| Unnecessary I/O | Ratio of I/O to CPU for the current query | Number |
| Username | Name of the user who submitted the query | String |
| Workload | Workload in which the query is running | String |