Incremental Planning and Execution (IPE) is a request processing method designed for complex requests. In IPE, Vantage breaks requests into smaller pieces and then optimizes each piece one at a time. The results from earlier request pieces help Vantage plan how to process later request pieces.
- Dynamic Plan
- Because Vantage can "learn" from the results of earlier request pieces, an IPE plan is called dynamic.
- Static Plan
- A static plan optimizes requests as a single unit. A static plan may provide some IPE functionality, but TDWM will work from the static plan.
Vantage applies IPE automatically to qualifying complex requests.
You can use IPE as a classification criterion for workload, filter, and throttle rules. This allows you to identify IPE requests being executed and manage them differently from non-IPE requests. You can use the NumFragments field in DBC.DBQLogTbl to identify IPE requests. NumFragments reports the number of fragments (pieces) for IPE requests. This field is null for non-IPE requests.
Because an IPE dynamic plan gives TASM only a partial view of a request, TASM ignores the following step-level criteria when attempting to classify an IPE request:
- Step estimated row count (minimum or maximum)
- Step estimated time (minimum or maximum)
- Full-table scan
- Join type
- IPE request criteria