The General view on the ruleset toolbar displays general attributes of a ruleset. The following tabs in the General view allow you to change settings when creating, editing, cloning, or viewing a ruleset:
- Ruleset name and description.
- Users, accounts, and profiles whose queries are allowed to bypass system filters and throttles.
Option Description Source Type Type of query source. You can select one or more items from each available source type. The dbc and tdwm user names cannot be removed. Filter Limits your choices in the source list. Items Lists the names of all available query sources of the selected type. Bypass Selected sources, listed by source type. Queries from each of the listed query sources bypass system filters and throttles for this ruleset.
- Limits/Reserves (TASM, Advanced Tier License for Teradata IntelliFlex, and Advanced Tier License for EDW)
- In SLES 11, you can limit the resources available to the system per planned environment. Limits are defined as a percentage of CPU or I/O. You can also reserve AWTs for use by the system per planned environment.
Option Description CPU Limit Percentage of CPU that the system can use. I/O Limit Percentage of I/O that the system can use. Reserved AWTs Maximum number of AWTs to reserve for tactical workloads. Max AWTs for new work Maximum number of AWTs for new tactical work.If you are using Workload Management Capacity on Demand (WM COD) with a contractual agreement in place, a special form of enforcement may have been configured outside the Workload Designer portlet by Teradata Customer Services, using special hardware COD packages. For Advanced Tier license, the COD flag must be set to yes in Teradata Database. These special enforcement COD settings can only be set at a fixed percentage of 12.5% units. After they are set, these hardware-enforced limits appear in parentheses on the Limits/Reserves tab. The values selected by the administrator for WM COD CPU and I/O limits within Workload Designer must be lower than or equal to the hardware COD settings. Workload Designer will not allow WM COD settings that are higher than the enforcement COD settings put in place by CS. If a pre-existing ruleset has WM COD limits set higher than these enforcement COD limits, the ruleset can be activated, but the lower hardware COD limits will override the specified WM COD values within Viewpoint.
- Reserves (IWM)
- You can reserve AWTs for use by the system per planned environment.
Option Description Reserved AWTs Maximum number of AWTs to reserve for tactical workloads. Max AWTs for new work Maximum number of AWTs for new tactical work.
- You can change the settings for intervals, blockers, activation, timeshare decay, throttle delay prevention, throttle delay queue order, increased job and resource limits, and available AWTs definition.
- Collection and reporting intervals.
Option Description Event Interval How often event thresholds are checked.If system or workload events have Simple or Averaging qualification times, then the event interval must be less than or equal to the lowest qualification time for any of the events. Dashboard Interval How often workload statistics are collected. Logging Interval How often workload and exception logs are written. Exception Interval How often exception thresholds are checked. Flex Throttle Action Interval (Teradata Database 16.0 and later for SLES 11 EDW systems) How often the availability of system resources is checked. Must be a multiple of the Event Interval.
- Settings for responding to throttled blockers. The log is located at DBC.TDWMEventLog. Selecting Log only logs the blocker. Abort or Release logs the action after the abort or release occurs.
Option Description Block Cycles Number of intervals over which the query must be blocked before the specified Block Action is taken. Block Action Action to perform in response to query blocking.
- Options available when the ruleset is activated. The feature is available when the option is selected. The Events and States feature is available by default and cannot be disabled.
Option Description Filters and Utility Sessions Filters reject user queries. Utility Sessions limit the number of sessions a specific utility can use. System Throttles and Session Control System throttles delay or reject queries at the system level. Session Control makes it possible to create session parameters. Workloads Workloads group queries that share characteristics so that a set of workload management controls can be applied to the group. Workloads are always available in SLES 11. Events and States Events are occurrences that trigger a response from the system. States are intersections of health conditions and planned environments.
- Timeshare Decay
- In SLES 11, you can enable timeshare decay, which automatically decreases the resource access rate of long-running queries in a Timeshare workload over time.
- Prevent Mid-Transaction Throttle Delays
- For Teradata Database 15.0 and later, select this option to allow subsequent queries within a transaction to run if there is a lock higher than an Access lock on a database object, thus allowing requests to not be delayed by workload throttles.
- Order the Throttle Delay Queue
- In Teradata 15.10 SLES 11, you can choose the order in which queries are released from the throttle delay queue.
Option Description By time delayed The longer a query has been delayed, the sooner it will be executed. By workload priority The higher the workload priority of a query, the sooner it will be executed.
- Utility Limits
- Teradata Database 15.10 and later supports increased MLOADX job limits and increased AWT resource limits. When the check box is selected, the limit for MLOADX jobs increases from 30 to 120 and the limit for AWT resources increases from 60 to 70.
- Clearing the check box decreases the maximum allowable resource and job limits for MLOADX jobs. The system uses the lower limits for job limits and AWT resources regardless of the ruleset configuration in this circumstance. If you clear the check box, make sure the limits for MLOADX jobs are less than the maximum ( ) and that resource limits are less than the maximum ( ).
- Define Available AWTs as
- If you are using Teradata Database 16.0 and later, you can designate the definition used in determining available AWTs.
Option Description AWTs available for the WorkNew (Work00) work type AWTs available for the WorkNew (Work00) work type. The WorkNew (Work00) work type is limited to 50 AWTs by default. If AWTs that can support WorkNew message are already in use servicing WorkNew message types, there may s0ll be AWTs in the unreserved pool that will not be considered available. AWTs available in the unreserved pool for use by any work type AWTs available in the unreserved pool for use by any work type. This is number of AWTs available in the unreserved pool able to be used by all work types, not limited to WorkNew work types.