Usage Notes - Teradata VantageCloud Lake

Lake - Database Reference
Deployment
VantageCloud
Edition
Lake
Product
Teradata VantageCloud Lake
Release Number
Published
February 2025
ft:locale
en-US
ft:lastEdition
2025-11-21
dita:mapPath
ohi1683672393549.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
ohi1683672393549

The QryLogSummaryV view of DBQLSummaryTbl holds the counts logged for queries of users with THRESHOLD or SUMMARY rules, and is populated only if summary information is requested or a threshold value is used.

Possible Values for ValueType

The THRESHOLD criterion is as follows:

Value Description
C AMP CPU seconds.
H Elapsed hundredths of a second.
I I/O count.
N Normalized AMP CPU seconds.
S Elapsed time in seconds.

LowHist and HighHist

Value Description
HighHist
  • Highest value for the SUMMARY option.
  • Zero for the THRESHOLD option.
  • If the modifiers CPUTIME or IOCOUNT are used, then this value is the highest CPU seconds or I/O counts set by the user.

    Use CPUTIMENORM for hundredths of a second of normalized CPU time. To measure subsecond queries, use ELAPSEDTIME. The default, elapsed time in seconds, can be explicitly specified with ELAPSEDSEC.
LowHist
  • Lowest value for the SUMMARY option.
  • For the THRESHOLD option, this is the threshold time set by the user. The default time is 5.
  • If the modifiers CPUTIME or IOCOUNT are used, then this value is the lowest CPU seconds or I/O counts set by the user. Use CPUTIMENORM for hundredths of a second of normalized CPU time. To measure subsecond queries, use ELAPSEDTIME. The default, elapsed time in seconds, can be explicitly specified with ELAPSEDSEC.

For the SUMMARY case, a row exists for each collection if the count of the queries run in that time frame (LowHist to HighHist) is greater than 0.

For the THRESHOLD case, one row (with LowHist=TypeofCriterion and HighHist=0) exists for the collection if there were queries shorter than LowHist seconds.