Data from DBC DBQL tables is first loaded in DBQL temporary tables and then into DBQL history tables.
The following table shows the relationship between temporary DBQL tables and DBQL history tables.
Note: You need to create temporary and history tables to archive DBQL data. Temporary and history tables are not system tables automatically included in the Data Dictionary.
|
SYS_MGMT Tablename |
Loaded From |
Used to Load |
Used to Delete |
Primary Index |
|
DBQLOGTBL_TMP |
DBC.DBQLOGTBL |
DBQLOGTBL_HST |
DBC.DBQLOGTBL |
ProcId CollectTimeStamp |
|
DBQLOGTBL_HST |
DBQLOGTBL_TMP |
|
|
LogDate QueryID ProcID |
|
DBQLSQLTBL_TMP |
DBC.DBQLSQLTBL |
DBQLSQLTBL_HST |
DBC.DBQLSQLTBL |
ProcID CollectTimeStamp |
|
DBQLSQLTBL_HST |
DBQLSQLTBL_TMP |
|
|
LogDate QueryID ProcID |
|
DBQLOBJTBL_TMP |
DBC.DBQLOBJTBL |
DBQLOBJTBL_HST |
DBC.DBQLOBJTBL |
ProcID CollectTimeStamp |
|
DBQLOBJTBL_HST |
DBQLOBJTBL_TMP |
|
|
LogDate QueryID ProcID |
|
DBQLOBJTBL_SUM |
DBQLOBJTBL_TMP |
|
|
LogDate UserName ObjectID ObjectNum |
|
DBQLSummaryTBL_TMP |
DBC.DBQLSummaryTBL |
DBQLSummaryTBL_HST |
DBC.DBQL |
ProcID CollectTimeStamp |
|
DBQLSummaryTBL_HST Note: The PI of the DBQLSummaryTBL_HST is as shown here because there is no good PI that offers a primary index retrieval or AMP local Joins and guarantees good distribution. |
DBQLSummaryTBL_ TMP |
|
|
ProcID CollectTimeStamp |