- Dynamic Plan
- Because Teradata Database 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.
Teradata Database 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.
- Step estimated row count (minimum or maximum)
- Step estimated time (minimum or maximum)
- Full-table scan
- Join type
- IPE request criteria