17.00 - 17.05 - Archiving DBQL Data - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Database Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.00
17.05
Published
June 2020
Language
English (United States)
Last Update
2021-01-22
dita:mapPath
rgu1556127906220.ditamap
dita:ditavalPath
lze1555437562152.ditaval

If your DBQL table archives are defined as PPI tables, do the following:

  1. Archive DBQL data nightly. This is strongly recommended so that the DBQL logs do not take up space in DBC and impact the system.
  2. Add a log date to each row. The log date is used as the partitioning column and makes querying the archived data much faster.
  3. Change the primary indexes. This is done to avoid table skewing.

You can also separate historical data from junk queries to make your DBQL table archives more concise.