Domain precedence for activity thresholds

Activity thresholds apply to individual activities. If multiple thresholds apply to the same executing activity, a decision about which threshold to enforce must be made.

Aggregate thresholds are not affected because the same activity can contribute to multiple activity aggregates simultaneously, as occurs with concurrency thresholds, for example.

The resolution about which activity threshold to apply to an executing activity follows the rule that a value defined in a local domain overrides any value from a wider or more global domain. The hierarchy of domains is as follows, from the most local to the most global:
  1. Statement
  2. Work action (at workload level)
  3. Workload
  4. Service subclass
  5. Service superclass
  6. Work action (at database level)
  7. Database

The following example shows how thresholds are overridden:

Examples

The following example shows how thresholds are overridden:
  • A threshold that defines a maximum execution time of 1 hour for all database queries defined in the database domain is overridden by a threshold that defines a maximum execution time of 5 hours for a service superclass set up to handle large queries.
  • That same service superclass threshold is overridden by a threshold for very large queries that defines the maximum execution time for a service subclass to be 10 hours.
  • The maximum execution time of 1 hour defined in the database domain can be overridden by a value of 10 minutes in a second service superclass geared towards ensuring that shorter, important queries can complete quickly.
  • The execution of a statement with text that matches the text that is specified for a threshold in the statement domain results in a threshold violation that overrides all other thresholds.