Recommendations for General Parameters | Teradata Vantage - 17.10 - Key Recommendations for General Parameters - Advanced SQL Engine - Teradata Workload Management

Teradata Vantageā„¢ - Workload Management User Guide

Advanced SQL Engine
Teradata Workload Management
Release Number
Release Date
July 2021
Content Type
User Guide
Publication ID
English (United States)
For an initial implementation, Teradata recommends that you use the defaults on the Bypass, Limits/Reserves, and Other tabs. Teradata also has the following recommendations for the General Parameters area.
Setting Recommendation
  • For Block Action, try Release. It allows for some concurrency management while causing minimal disruption to running requests. You can try another setting later if needed.
  • For Block Cycles, use 1.
  • Create views with the LOCKING FOR ACCESS modifier. This allows read-only users and users who modify the data to have concurrent access. Use of access locks prevents deadlocks and improves performance.
Bypass A typical practice is to set Bypass for BAR work and critical DBA activities. Bypassing BAR work does not bypass utility session limits.
  • Teradata recommends that you use the default interval settings unless you have a reason not to.
  • Set the Event Interval to no lower than 30 seconds for systems with more than 500 AMPs.
  • Set the Exception Interval to equal to or less than the MONITOR SESSION rate. Do not set the Exception Interval to lower than 6 seconds.
Users DBC and TDWM are included in the bypass list by default. System filters and throttles do not apply to them. If other users are affected by system filters and throttles in a way that does not meet workload management goals, adjust system filter and throttle classification criteria so that these users, account names/strings, or profiles are not affected. Avoid using the bypass list to make exceptions for users because that may result in situations where the necessary system filters and throttles are not applied.