Collecting historical data for performance

ResUsage History
Teradata Manager can summarize key ResUsage data up to 1 row per system per time
period specified. Teradata recommends retaining 3 to 6 months of detail to accommodate
various analysis tools, such as Teradata Manager itself, Visual Edge, and so on.

AMPUsage History
Teradata Manager can summarize to 1 row per system per account per time period
specified. Moreover, it can retain 1 day of detail. Teradata recommends deleting excess
detail to keep ongoing summary collection efficient.

DBQL History
Teradata Manager summaries key DBQL data to 1 row per user / account / application ID
/ client ID per time period. Teradata recommends retaining 13 months of copied detail.
That is, Teradata recommends copying detail to another table daily. You should delete the
source of copied detail daily to keep online summary collection efficient.

Leave a Reply

Your email address will not be published. Required fields are marked *