How can the Administrator effectively throttle these stored procedures?

BATCH_USER submits stored procedures, utility jobs, and other requests. All BATCH_USER work

classifies into workload WD-Batch based on username criterion.

System performance has slowed due to AWT exhaustion during the batch window. The Administrator determined the AWT exhaustion is due to high concurrency of stored procedure calls from BATCH_USER.

How can the Administrator effectively throttle these stored procedures?
A . Create a utility limit, classify on username = BATCH_USER and utility = Stored Procedure, and set the limit.
B . Define an AWT resource limit, classify on username = BATCH_USER and utility = Stored Procedure, and set the limit.
C . Create a new workload, classify on username = BATCH_USER and statement type = CALL, and set a throttle.
D . Define a system throttle, classify on username = BATCH_USER and stored procedure = *.*, and set the limit.

View Answer

Answer: C

Explanation:

In this scenario, the issue arises due to high concurrency of stored procedure calls, which are exhausting AWTs (AMP Worker Tasks). To address this, the administrator needs to throttle the specific stored procedure calls made by BATCH_USER. The most effective way to do this is to create a new workload that specifically targets those calls (statement type = CALL) from BATCH_USER and then applies a throttle to limit concurrency. This helps manage the system’s AWTs by controlling how many stored procedures can be run concurrently.

Other options are less suitable as they either do not target stored procedures specifically or may not provide the necessary granularity in controlling AWT usage for stored procedure calls.