16.10 - Weekly and/or Daily Reports - Teradata Database

Teradata Database Administration

Product
Teradata Database
Release Number
16.10
Published
April 2018
Language
English (United States)
Last Update
2018-04-26
dita:mapPath
qjg1509413559832.ditamap
dita:ditavalPath
changebar_rev_16_10_exclude_audience_ie.ditaval
dita:id
ujp1472240543947

Weekly reports provide data on performance trends.

To make weekly and/or daily reporting effective, Teradata recommends that you establish threshold limits. Note that filtering on key windows having a 24-hour aggregate of weekly aggregates that includes low-used weekends and night hours distorts the report.

Furthermore, Teradata recommends that you analyze the longest period possible. This avoids misleading trend data by softening temporary highs and lows.

Below are examples of some of weekly reports and their sources:

  • CPU AV & Max from ResUsage

    This report provides data on the relationship between resources and demand.

  • CPU seconds by workload (account) from AMPUsage.
  • Throughput by Workload from DBQL

    This report provides data on how much demand there is.

  • General Response times from Heartbeat Query Log

    This report provides data on the general responsiveness of the system.

  • Response Time by Workload from DBQL

    This report provides data on how fast individual queries were responded to.

  • Active Query & Session Counts by Workload

    This report provides data on how many users and queries were active and concurrent.

  • CurrentPERM

    This report provides data on how data volume is or is not growing.

  • Spool

    This report provides data on how spool usage is or is not growing.

The above reports can, of course, be run daily.