Defining workloads based on application

With millions of queries coming in and out of Teradata Database, it becomes important to manage them better. Low-performance queries need to be demoted or aborted, and critical jobs should be completed as soon as possible.

Your windows also have a workload and process that you can control and give priority to. Kill an application that may have hung your Windows machine. It looks like something like the following image:

To cater for the need to prioritize the request and to make the system stable, use Teradata Active System Management (TASM). The user or batch queries are categorized in the workload. These workloads are then categorized based on their priority. And to further regulate queries in this workload, TASM has filter and throttle created in it.

The following diagram can be used to explain this in a better way:

TASM enables admins to set SLGs based on the application, to monitor adherence to them, and to take any necessary steps to reallocate resources...