The ESTIMATEDSQLCOST threshold specifies the maximum estimated
cost that is permitted for DML activities.
- Type
- Activity
- Definition domain
- Database, service superclass, service
subclass, work action, workload, and statement
- Enforcement scope
- Database
- Tracked work
- See the information later in this topic
- Queuing
- No
- Unit
- Estimated SQL cost expressed in timerons
- Predictive or reactive
- Predictive
This threshold tracks the following activities:
- DML activities that are issued at the coordinator member.
- Nested DML activities that are invoked from a user application.
Consequently, DML activities that are issued by the data server internally,
such as DML activities issued from within the DB2® utilities, SYSPROC stored procedures, and
internal SQL, are unaffected by this threshold unless their cost is
included in the parent activity estimate. In this situation, these
activities are indirectly tracked. A trigger is an example of an indirectly
tracked activity. IMPORT, EXPORT, and other CLP commands are considered
to be user logic. Activities that are invoked from within IMPORT,
EXPORT, and other CLP commands are subject to thresholds. For information
about the activities that fall under a work class with the DML work
type, see Work identification by type, cost, or data accessed with work classes.
DB2 Version 10.1 for Linux, UNIX, and Windows