For TASM in Teradata 12 it is not enough to set the enforcement priority to tactical. You must explictly expedite the allocation group. This is done in the GUI screen that shows all the workload management setup, including RP, AG, AG relative weight, and WD. If a AG/WD has a tactical enforcement priority, it will have a checkbox under a column named "expedite". If you check that column then requests within that AG/WD will use the work08/09 work types.
As you have discovered, that is not necessary in Teradata 14. Once you make the AG/WD as tatical, it is automatically expedited and will use Work08 work types.
WorkTypeMax08 has nothing to do with the the number of reserved AWTs that you select. WorkTypeMax08 is reporting the maximum number of tasks that were using work08 within that logging interval, but it is not telling you how many of those tasks were using AWTs from the reserve pool for expedited queries, or how many were using AWTs from the unassigned pool.
You have to explicitly select a reserve count in order for work08 tasks to use a reserved AWT. When you select a reserve count, that is the number of AWTs that will go into a special reserve pool. Work08 tasks can draw AWTs from that pool, but if that pool is empty they will try to draw AWTs out of the unassigned pool.
You can set the reserve count at 2 and still have 10 or 20 or 30 tasks running in the work08 work type. Those are two different things. The fact that WorkTypeMax08 = 6 does not tell you what the tactical reserve count is. It could be there are zero tactical reserves, but if there are expedited workloads that are doing work, you will see usage in work08 even with no reserves defined.
The limit of 20 you mention is for the number of reserved AWTs you are able to define. But you can have a greater number of tasks running that use the work08 work type. If that happens, all of them will not be able to count on having a reserved AWT waiting for them and will attempt to use an AWT from the unassigned pool.
Max Expedited AWTs puts a limit on how many tasks will be allowed to start up using the work08 work type. The default is 50, because there is a similar limit of 50 on how many tasks can be active using the worknew work type. This number of 50 has no relationship with the number of reserved AWTs you can select. It only controls how many tasks can use the work08 work type at one time, whether or not they are able use a reserved AWT for their work.
Thanks, -Carrie
For TASM in Teradata 12 it is not enough to set the enforcement priority to tactical. You must explictly expedite the allocation group. This is done in the GUI screen that shows all the workload management setup, including RP, AG, AG relative weight, and WD. If a AG/WD has a tactical enforcement priority, it will have a checkbox under a column named "expedite". If you check that column then requests within that AG/WD will use the work08/09 work types.
As you have discovered, that is not necessary in Teradata 14. Once you make the AG/WD as tatical, it is automatically expedited and will use Work08 work types.
WorkTypeMax08 has nothing to do with the the number of reserved AWTs that you select. WorkTypeMax08 is reporting the maximum number of tasks that were using work08 within that logging interval, but it is not telling you how many of those tasks were using AWTs from the reserve pool for expedited queries, or how many were using AWTs from the unassigned pool.
You have to explicitly select a reserve count in order for work08 tasks to use a reserved AWT. When you select a reserve count, that is the number of AWTs that will go into a special reserve pool. Work08 tasks can draw AWTs from that pool, but if that pool is empty they will try to draw AWTs out of the unassigned pool.
You can set the reserve count at 2 and still have 10 or 20 or 30 tasks running in the work08 work type. Those are two different things. The fact that WorkTypeMax08 = 6 does not tell you what the tactical reserve count is. It could be there are zero tactical reserves, but if there are expedited workloads that are doing work, you will see usage in work08 even with no reserves defined.
The limit of 20 you mention is for the number of reserved AWTs you are able to define. But you can have a greater number of tasks running that use the work08 work type. If that happens, all of them will not be able to count on having a reserved AWT waiting for them and will attempt to use an AWT from the unassigned pool.
Max Expedited AWTs puts a limit on how many tasks will be allowed to start up using the work08 work type. The default is 50, because there is a similar limit of 50 on how many tasks can be active using the worknew work type. This number of 50 has no relationship with the number of reserved AWTs you can select. It only controls how many tasks can use the work08 work type at one time, whether or not they are able use a reserved AWT for their work.
Thanks, -Carrie