SLES 11 Adjusting Tactical Workload Exceptions - Teradata Database - Teradata Viewpoint

Workload Pre-Migration User Guide

Teradata Database
Teradata Viewpoint
January 2016
English (United States)
Last Update
Product Category
Analytical Ecosystem
In SLES 11, when you create a tactical workload, a tactical exception is automatically created to prevent a high-consuming query from depriving tactical workloads of system resources. Tactical exceptions cannot be deleted, but you can modify them if your environment has different needs.

Tactical exceptions occur when both threshold criteria are exceeded for either Tactical CPU Time or Tactical I/O Physical Byte. Tactical exceptions trigger an action that moves a high-consuming query to another workload and can trigger other actions, such as issuing an alert or running a program. Tactical exceptions apply to the tactical workloads they are associated with, across all environments.

  1. From the ruleset toolbar, click Workloads.
  2. Select or create a tactical workload.
  3. Click the Tactical Exception tab.
  4. Under Criteria, enter thresholds for Tactical CPU Time and Tactical I/O Physical Byte.
  5. Under Action, select a workload. The query is moved to this workload when a query exceeds both Tactical CPU Time and Tactical I/O Physical Byte thresholds.
  6. [Optional] Under Notifications, enable any of the following options for the start or the end of the event:
    Notification Description
    Send Alert Specifies the action to trigger.
    Run Program Specifies the Alerts registered programs to trigger.
    Post to QTable The string you enter is posted to the QTable.
  7. Click Save.