I don't see anything problematic with your evaluation order. You have the workloads with the most restrictive classifications first, which is good. The only way that an Analyze job could fall through to the H workload that I can think of is if for some reason query bands were not working
You could check whether or not the query bands are being recognized. Find the analyze job in DBQLogTbl output. There is a query band field. If QueryBand in DBQLogTbl is blank for the Analyze job it means the query band value did not get picked up by the Analyze job.
If you think the AutoStats feature is not working as you expect, please open an incident with the support center.
I don't see anything problematic with your evaluation order. You have the workloads with the most restrictive classifications first, which is good. The only way that an Analyze job could fall through to the H workload that I can think of is if for some reason query bands were not working
You could check whether or not the query bands are being recognized. Find the analyze job in DBQLogTbl output. There is a query band field. If QueryBand in DBQLogTbl is blank for the Analyze job it means the query band value did not get picked up by the Analyze job.
If you think the AutoStats feature is not working as you expect, please open an incident with the support center.
Thanks, -Carrie