Resource consumer group
As we saw in Chapter 3, a job class is mapped on a resource consumer group. So, it makes sense to start defining resource consumer groups now.
First, think about how you want to control the various tasks and how you want them to interact with each other—or even better, how to not interact with each other. Which jobs should get more resources than other jobs? Which users should get a higher priority over the others, and why?
As most users in a database will be regular online users, we can keep them in a default group that gets the second-highest priority. For those few users who tend to mess up the system, we can create a separate group and isolate them from the rest. Resource Manager can guarantee resources for particular resource consumer groups.
The resources not used at priority level 1 will be redistributed at priority level 2, and the remaining resources will be divided further. This can go on for eight priority levels. Take a look at this screenshot:
The image...
