Advantages of Manually Flushing Query Logs - Analytics Database - Teradata Vantage

SQL Data Definition Language Detailed Topics

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2024-10-04
dita:mapPath
vuk1628111288877.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
jbg1472252759029
lifecycle
latest
Product Category
Teradata Vantage™

Using FLUSH QUERY LOGGING requests synchronously flushes all DBQL and TDWM caches across the whole system. All the PEs flush respective caches at the same time. When a FLUSH QUERY LOGGING request returns a success response to the client, the cache contents are written to their respective tables.

Note that submitting FLUSH QUERY LOGGING requests too frequently has the same negative performance impact as setting the DBS Control DBQL flag too low.

FLUSH QUERY LOGGING enables all the DBQL and TDWM caches to be flushed synchronously and does not return control to the client until all the caches have been flushed into the appropriate tables.