Posted 10 Dec 2014
Note: This content only applies to releases earlier than Teradata Database 14.10.05. If you are on Teradata Database 14.10.05 or later releases, please look at the more recent posting titled: A New Simplified Approach to Parsing Workload Selection.
When you think about priorities, you probably focus your attention on AMP work. Whether you are using Teradata Active System Management (TASM) or Teradata Integrated Workload Management (TIWM), AMP work performed by requests are typically spread across different workloads, with their priorities based on the importance of the work to the business and how long you expect the work to run.
Parsing engine work on behalf of a query runs within a workload as well. Work performed on the parsing engine is typically very quick and requires very few resources. So why not run some, or all, of your parsing activity in a very high priority workload where it may be able to complete sooner when your system is busy, just as you do with your short, critical AMP work? This posting will explain how parsing priority is determined, and will illustrate the steps involved in increasing parsing priority.