In TimeXtender it is possible to create derived tables or subselections of tables which could benefit from automatically created covering indexes. Indexes are already created to drive Conditional Lookups but should also be possible for:
- Aggregate tables: especially if a small subset of fields are taken or if Data Selection rules are applied to the Aggregate
- Data movement: whenever only a portion of fields is taken across or Data Selection rules are applied
Covering indexes would make Execution faster and require less investigation effort once reloads start slowing down.
Due to complete lineage being available for these TimeXtender automations, it should be possible to generate correct indexes. It is probably also beneficial to give the user the choice whether or not such an index should be added.
