Although any of the threshold types that can be used in work actions can be associated with any work class, not all types of database activities are supported for all of those threshold types.
For example, if you create a work class for DDL, then associate that work class with an ESTIMATEDSQLCOST threshold work action, that threshold will not apply to any of the requests that are classified under DDL because DDL statements do not have an estimated cost. If you create a work class for ALL, then associate that work class with an ESTIMATEDSQLCOST threshold work action, although all database activities belong to the ALL work class, the threshold will only apply to the database activities that have an estimated cost.
ACTIVITYTOTALTIME threshold | ESTIMATEDSQLCOST threshold | CONCURRENTDBCOORDACTIVITIES threshold | CPUTIME threshold | |
---|---|---|---|---|
READ, including SET statements with embedded READ SQL | Yes | Yes | Yes1 | Yes |
WRITE, including SET statements with embedded WRITE SQL | Yes | Yes | Yes1 | Yes |
CALL | Yes | No | No | Yes |
DML, including SET statements with embedded READ or WRITE SQL | Yes | Yes | Yes1 | Yes |
DDL | Yes | No | Yes1 | No |
LOAD | Yes | No | Yes1 | No |
ALL | Yes | Some | Yes1 | Some |
SQLROWSREAD threshold | SQLROWSRETURNED threshold | SQLTEMPSPACE threshold | |
---|---|---|---|
READ, including SET statements with embedded READ SQL | Yes | Yes | Yes |
WRITE, including SET statements with embedded WRITE SQL | Yes | Yes | Yes |
CALL | No | No (see note) | No |
DML, including SET statements with embedded READ or WRITE SQL | Yes | Yes | Yes |
DDL | No | No | No |
LOAD | No | No | No |
ALL | Some | Some | Some |