IBM FileNet P8, Version 5.2.1            

Not every property needs to be indexed

Do not attempt to cover the entire set of SELECT or WHERE columns with a large composite index or SQL Server "include columns". Such a solution is expensive in terms of storage costs, ingestion overhead, and statistics run time. Also, future changes might break the solution when either user or system property columns are added to the SELECT list. These changes might occur during Content Platform Engine upgrades, metadata authoring, or changes in the search.

Tip: For performance improvement suggestions for a query such as the following one, see Index tuning: Selective search conditions.
Table 1. Sample query
Content Platform Engine SQL Corresponding database SQL
SELECT Id, Property1, Property2, ... 
FROM Document 
WHERE Property1 = 'value' 
AND Property2 = 'value' ... 
The database SQL contains more WHERE clauses on home_id, object_class_id as well as other system columns such as is_current, depending on the search.


Last updated: October 2015
p8ppt284.htm

© Copyright IBM Corporation 2015.