IBM FileNet P8, Version 5.2.1            

Unnecessary indexes

Slow query performance can sometimes be preferable to the costs that are imposed by property indexes. This trade-off is especially relevant for queries whose search conditions reference dozens of properties. Property indexes can cause object creation to be slower and also add to storage costs.

Instead of creating one or more database indexes, running a query off-hours might be the better solution in the following circumstances:

If a high percentage of the table rows satisfies the search conditions, a query might not use a database index even if it exists: the database query optimizer might decide that the best query execution plan is to use a table scan rather than property indexes. But there are no fixed rules for when an index is needed or not needed. As discussed in these tuning guidelines, some indexing solutions still help search performance even if many rows satisfy the search conditions.



Last updated: October 2015
p8ppt282.htm

© Copyright IBM Corporation 2015.