In a previous chapter, we introduced the concept of workload and explored how Teradata workload management classifies requests (queries) into workloads. We briefly mentioned that resource allocation (CPU seconds and IOs) is one of the primary reasons for grouping requests.
We introduced Teradata's two kinds of workload managers (TIWM and TASM) and talked about how they are different and what they have in common.
This chapter will delve deeper into the Teradata priority scheduler and its role in distributing resources across workloads and requests. The priority scheduler is the software responsible for assigning available resources to active requests.