Query logging data is off-loaded to your own object storage. For help with troubleshooting using that data or query optimization, you can grant Teradata access to views in the table that follows. These views are for Teradata use only.
The Teradata employee must first be granted SELECT on td_metric_svc:
GRANT SELECT ON td_metric_svc to td_user;
| View | Description |
|---|---|
| dbqlexplain_operationsv | Contains the explain information in an unformatted string without line breaks. This view is used by Teradata employees only. |
| dbqlobj_operationsv | Stores information on the target objects of the query being logged. One row is logged for each object referenced by the query. This view is used by Teradata employees only. |
| dbqlog_operationsv | The main table containing information about queries being logged. This view is used by Teradata employees only. |
| dbqlsql_operationsv | Stores the full SQL text of the query. One query string may require more than one row. This view is used by Teradata employees only. |
| dbqlstep_operationsv | Stores information about each processing step used to satisfy the query. One row is logged for each step, including parallel steps. This view is used by Teradata employees only. |
| dbqlsummary_operationsv | Stores information about queries that meet the criteria for a rule specifying the LIMIT SUMMARY or LIMIT THRESHOLD option. This view is used by Teradata employees only. |
| dbqlutility_operationsv | Each row stores information about one completed load/export or Data Stream Architecture job. This view is used by Teradata employees only. |