1,126
edits
(Added IBM CMOD Performance image, corrected spelling mistakes.) |
(Corrected typos, added section on IBM CMOD query.) |
||
| Line 22: | Line 22: | ||
= Selecting fields = | = Selecting fields = | ||
When selecting which Application Group field to add to the composite index, the order of the fields is extremely important. Use the field that has the highest | When selecting which Application Group field to add to the composite index, the order of the fields is extremely important. Use the field that has the highest cardinality (the most unique values or the fewest repeated values) generally followed by the date. This combination allows searches to identify documents quickly, and also zero-in on a specific date range as well. Optimizing the use of Content Manager OnDemand composite indexes requires research into the types of queries that users are performing in OnDemand. Your Database Adminstrator responsible for IBM CMOD will have access to utilities to help determine how best to achieve better Content Manager OnDemand performance. | ||
= Impact on Storage = | = Impact on Storage = | ||
Composite indexes will require that you store the contents of both columns, along with a list of database page identifiers. If your IBM CMOD Application Group is especially large, this can cause the database to consume anywhere from 10 to 50% more space. Check with your Database Administrators and System Administrators to ensure that you have enough space to complete the index creation. | Composite indexes will require that you store the contents of both columns, along with a list of database page identifiers. If your IBM CMOD Application Group is especially large, this can cause the database to consume anywhere from 10 to 50% more space. Check with your Database Administrators and System Administrators to ensure that you have enough space to complete the index creation. | ||