Database Query Log is an extremely useful tool to the Teradata DBA in terms of analysing resource usage as well as for security purposes.
Basically it is a log of queries submitted by users of the Teradata Database. It can record varying levels of detail but includes CPU usage, I/O and elapsed time and details of the objects accessed.
DBQL Step data can help a DBA drill deeper into a problem query by showing which query step is causing the problem skewing, product joining or large scan. This data, when matched up with the EXPLAIN plan, can provide the insight needed to tune the query.
Highlights
Allow you to log query processing activity for later analysis. SQL and other metrics are captured
DBQL captures details and metrics for workload analysis and performance tuning purposes
DBQL comes with empty pre-defined tables.
The DBA sets up rules to what information DBQL should capture and then turns DBQL ON !
The empty pre-defined tables now begin to fill up with the information the DBA said to capture
The DBA can tell DBQL to capture SQL statements, what objects were referenced, thresholds and summary rules, Explain steps, query exceptions
defined in workloads, and other important metrics
THe DBA has choices and can turn on or turn off DBQL or the DBA can only capture one person, an Accounting group, workload, or everyone. DBQL works
great to help define of redefine workloads!
Basically it is a log of queries submitted by users of the Teradata Database. It can record varying levels of detail but includes CPU usage, I/O and elapsed time and details of the objects accessed.
DBQL Step data can help a DBA drill deeper into a problem query by showing which query step is causing the problem skewing, product joining or large scan. This data, when matched up with the EXPLAIN plan, can provide the insight needed to tune the query.
Highlights
Allow you to log query processing activity for later analysis. SQL and other metrics are captured
DBQL captures details and metrics for workload analysis and performance tuning purposes
DBQL comes with empty pre-defined tables.
The DBA sets up rules to what information DBQL should capture and then turns DBQL ON !
The empty pre-defined tables now begin to fill up with the information the DBA said to capture
The DBA can tell DBQL to capture SQL statements, what objects were referenced, thresholds and summary rules, Explain steps, query exceptions
defined in workloads, and other important metrics
THe DBA has choices and can turn on or turn off DBQL or the DBA can only capture one person, an Accounting group, workload, or everyone. DBQL works
great to help define of redefine workloads!
No comments:
Post a Comment