After upgrading from SLES 10 to SLES 11, use the Workload Designer portlet in Teradata Viewpoint to review and modify as necessary the results of workload migration. Pertinent activities may vary based on licensing.
For detailed information on any of the configuration activities, see Teradata Viewpoint User Guide, as well as the following Orange Books:
- Teradata Active System Management For Teradata 15.0 with SLES 11, 541 -0009281- C01
- Teradata Active System Management For Teradata 14.10 with SLES 11, 541 - 0009281- B02
- Teradata Integrated Workload Management Appliances and Enterprise Data Warehouse for Teradata Database 14.10 with SLES 11, 541-0009612 - B03
License-Independent Post-Upgrade Configuration
The following post-upgrade workload-management configuration activities may be pertinent regardless of system licensing.
- Distributing qualifying workloads to the Tactical tier. This tier should be reserved for single or few-AMP, highly critical workloads with response-time requirements of one second or less.
- Changing the access level assigned to timeshare workloads.
- Adjusting tactical workload exceptions.
- Setting planned environment reserve values.
Configuration after Upgrading from a SLES 10 Appliance- or PSF-Licensed System
If you upgraded from a SLES 10 appliance-licensed or PSF-licensed system, the following post-upgrade workload-management configuration activities may be pertinent, regardless of SLES 11 system licensing.
- Breaking one or more of the four automatically created timeshare workloads into multiple workloads of your own configuration to achieve finer granularity in such areas as throttling, filtering, monitoring, and reporting.
- Enabling the timeshare decay option to emulate the functionality of query milestones, which are not maintained upon upgrade.
- Setting different values for or deleting the throttles that are automatically created to limit system concurrence (that is, GeneralQuery, with a limit of 52, and OneSecondQuery, with a limit of 30).
Configuration after Upgrading to a SLES 11 TASM-Licensed System
If your SLES 11 system is licensed for TASM, the following post-upgrade workload-management configuration activities may be pertinent, regardless of SLES 10 system licensing.
- Distributing qualifying workloads to the SLG tier. This tier should be reserved for workloads that are secondary in importance to tactical workloads but are associated with a short service level goal or service level expectation; require a short response time due to business importance; and do not generally consume a significant amount of CPU resources.
- Distributing workloads across multiple SLG tiers. By default, only one SLG tier is provided, but you can add tiers up to a total of five.
- Allocating resources to SLG workloads at an adjusted percentage.
You can adjust SLG workload allocation percentages. Before doing so, however, consider that the SLG tier should be reserved for highly critical workloads that consume few resources. If some workloads that you have associated with the SLG tier are less critical to the business than others, consider moving those workloads to the Top access level of the Timeshare tier.
- Setting planned environment limit values.
- Creating virtual partitions in addition to the single, default Standard partition, if business conditions demand. In general, multiple virtual partitions should be reserved for dividing workloads based on business unit or geographic region, and not for enforcing priority among peer workloads. Up to 10 virtual partitions are allowed.
- Moving workloads between virtual partitions.
Configuration after Upgrading to a SLES 11 IWM-Licensed System
If your SLES 11 system is licensed for IWM, the following post-upgrade workload-management configuration activity may be pertinent.
- Using throttles to refine management of low priority workloads.