Defines the interval in seconds between flushings of the DBQL caches to the DBQL dictionary tables.
1 through 3600 seconds
Changes Take Effect
After the DBS Control Record has been written. However, DBQL will not become aware of the new setting until the current timer expires (or 10 minutes passes). Therefore, the change could take up to 10 minutes to become effective.
If an END QUERY LOGGING statement is issued, all the caches (except the DBQLSummary cache, which is flushed at the selected Flush Rate) are flushed as part of the END QUERY LOGGING statement.
If a FLUSH QUERY LOGGING statement is issued, the caches requested are flushed. To flush all the caches, use the All option in FLUSH QUERY LOGGING.
Example: Using the DBQLFlushRate DBS Control field
Assume that the DBQLFlushRate is 300 seconds. This means that the cache entries are written to the DBQL dictionary tables at least every 5 minutes. If a cache is filled up after 3 minutes, entries are written at 3 minutes and then again at the 5-minute interval.
|For more information on…||See…|
|BEGIN QUERY LOGGING, END QUERY LOGGING, and FLUSH QUERY LOGGING statements||Teradata Vantage™ - SQL Data Definition Language Syntax and Examples, B035-1144.|
|tracking processing behavior with the DBQL||Teradata Vantage™ - Database Administration, B035-1093.|
See also LockLoggerFlushRate.