Users are complaining that queries in their workload are taking too long. The Administrator suspects that workload management may be throttling the…

The ResUsageSawt (Scheduler Activity by Workload Type) table is specifically designed to monitor the activity of the Teradata workload management scheduler. It provides aggregated data at the workload level for specific time intervals. To confirm if queries are being throttled, an administrator would analyze the DelayTime and DelayCount columns in this table. These columns directly measure the total time and the number of requests that were held in a delay queue due to system or workload throttles, providing clear evidence of throttling's impact on the workload.

A. ResUsageSps: This table tracks resource usage (CPU, I/O) by workload, but it does not contain specific metrics like delay counts or times to confirm throttling activity.

C. DBQLogTbl: While this table has a DelayTime column for each individual query, ResUsageSawt is superior for analyzing the overall workload trend, as it provides aggregated delay statistics over time.

D. DBQLStepTbl: This table logs performance data for each step of a query after it has begun execution. Throttling occurs before the first step starts, so this table would not contain that information.

1. Teradata Vantage™ - Resource Usage Macros and Tables, Release 17.20, B035-1149-1121K, Chapter 3: Resource Usage Tables, Section: "ResUsageSawt".

Page 111: The document states, "The ResUsageSawt table logs scheduler activity by workload type... Use ResUsageSawt data to... Determine how often and how long requests are delayed by workload management throttles." This directly supports using ResUsageSawt to investigate throttling. The table definition on page 112 explicitly lists DelayTime and DelayCount as columns.

2. Teradata Vantage™ - Database Administration, Release 17.20, B035-1093-1121K, Chapter 13: Using DBQL to Monitor Query Performance, Section: "DBQLogTbl".

Page 428: This section describes the DelayTime column in DBQLogTbl as "Time in seconds the query was delayed by Teradata WM." This confirms that DBQLogTbl contains delay information, but it is on a per-query basis, making ResUsageSawt the more appropriate tool for workload-level analysis as implied by the question.

3. Teradata Vantage™ - Resource Usage Macros and Tables, Release 17.20, B035-1149-1121K, Chapter 3: Resource Usage Tables, Section: "ResUsageSps".

Page 115: The description for ResUsageSps states it "logs resource usage by priority scheduler partitions." The column definitions include metrics like CPUUServ and IOUnclass, confirming it tracks resource consumption, not scheduler delays.