A client has a healthy system but often sees delays in some queries because of workload concurrency limits. These limits have been carefully chosen…

Flex Throttles are a feature within Teradata Active System Management (TASM) specifically designed to manage workload concurrency dynamically. When a workload with a Flex Throttle enabled reaches its concurrency limit, it can "borrow" unused Amp Worker Task (AWT) slots from the system. This allows the workload to temporarily exceed its defined limit to process queries that would otherwise be delayed, without requiring a permanent modification to the carefully chosen base concurrency limit. This directly addresses the client's need for flexibility while maintaining their established workload rules.

A. Use a system throttle.

A system throttle imposes a global limit on all queries entering the database, which does not target the specific workload causing delays.

B. Use Query Group Viewpoint portlet to change the throttle limit temporally.

The Query Group Viewpoint portlet is used for monitoring and analysis of query groups, not for modifying workload definitions like throttle limits.

D. Use Query Monitor Viewpoint portlet to change query workloads.

This is a manual, reactive action on individual queries. It is not a systemic solution to automatically manage frequent delays caused by concurrency limits.

---

1. Teradata® Workload Management User Guide (Release 16.20, B035-1197-118K)

Section: Chapter 4: Workload Management Methods and Rules > Throttles > "Flex Throttles"

Content: "Flex throttles allow a workload to exceed its concurrency limit when there are available AWTs... When a workload with a flex throttle is at its concurrency limit, and a new query for that workload arrives, Teradata Database checks for available AWTs. If AWTs are available, the query is allowed to run, even though the workload concurrency limit is exceeded." This directly supports the use of Flex Throttles to handle delays without changing the base limit.

2. Teradata® Viewpoint User Guide (Release 16.20, B035-2206-118K)

Section: Chapter 11: Portlets > "Query Monitor"

Content: This section describes the Query Monitor portlet's functions, which include monitoring sessions and queries, and taking actions like aborting a query or changing its workload. This confirms it is a tool for manual intervention on specific queries, not a policy-based solution for concurrency.

3. Teradata® Viewpoint User Guide (Release 16.20, B035-2206-118K)

Section: Chapter 11: Portlets > "System Health"

Content: The description of system-level throttles confirms they are global settings: "The System Throttle... limits the number of concurrent requests that can execute on the system." This validates why option A is incorrect for a workload-specific issue.