Does the information in the DBQL tables represent 100% of the workload of a Teradata system?
No, because we can define which information should be stored and in which detail, as mentioned above. We can use filters for logging only the required information. Detailed information can be aggregated and is then only available in aggregated form. For performance reasons, the collected information is not real-time in the DQBL tables but is cached in memory and written at intervals (e.g., every 10 minutes). If the system restarts, all information that has not yet been written from the cache to the DBQL tables is lost. The DBSCOntrol option "DBQLFlushRate" controls in which intervals the cache is written to the DBQL tables. If we want to write the cache immediately, we can do it with the following command: FLUSH QUERY LOGGING WITH ALL;