This topic provides additional information about the Query Count data collector that may be helpful.
When enabling query logging, it is important to manage the size of the DBQL tables. Clearing the DBQL tables nightly is recommended. The queries performed by Teradata Viewpoint against DBQL require an all-row scan. If the size of the DBQL tables is not managed, queries against them can cause unnecessary use of Teradata Database resources. Teradata Professional Services has a Data Collection and Capacity Planning offering that includes the movement and cleanup of DBQL data on a nightly basis. If DBQL is not cleaned up nightly, using the Query Count collector is not recommended.
The Productivity portlet uses query count data to show total query counts and query counts by application hourly. The Today's Statistics portlet uses the data to show query counts and query log data for the last hour of collected data, grouped by duration. The Metric Heatmap portlet shows query count and query log data collected over the hour. The Workload Designer portlet uses this data to populate several select lists when creating classification criteria.
The default collection rate for querying DBQL is one hour. To get the portlets to display the most current query counts, you can increase the collection frequency, but at the cost of using more Teradata Database resources to query DBQL more frequently.