The DBQLRuleTbl and DBQLRuleCountTbl are archived and restored only if database DBC is migrated but none of the other DBQL tables are archived or restored. To migrate data from those tables, the tables must be copied into a user database/table. For more information about saving DBQL log data, see Database Administration, available from http://www.info.teradata.com.
Definitions of the DBQL log tables often change between major releases, and the data in DBQL log tables from a prior release does not get converted to match the data collected using the definitions in the subsequent release.
All of the DBQL rules that were present on the source system are save/restored, so the same information is collected on the destination system.
It may be helpful to take advantage of the Teradata Professional Services offering to set up standard DBQL rules and logging on the destination system.
The output from the script includes a dbql_out.rpt file. This file details how many rows currently exist in each of the DBQL tables, as illustrated in the following table.
| Table | Count |
|---|---|
| DBQLExplainTbl | 152478 |
| DBQLObjTbl | 3078221 |
| DBQLogTbl | 219991 |
| DBQLSqlTbl | 220024 |
| DBQLStepTbl | 1073967 |
| DBQLSummaryTbl | 0 |