PPM Support Tip: Missing indexes on Database tables
KCS article: KM00681040
Is it safe to add indexes to PPM specific tables (for example FM_FORECAST_ACTUAL_LINES or FM_FINANCIAL_LINE_CELLS) to increase performance on views joining on these tables if these indexes are missing?
It is safe to add custom indexes on DB tables FM_FORECAST_ACTUAL_LINES and FM_FINANCIAL_LINE_CELLS; the issue is related to product defect QCCR1L45264, which reports missing indexes on several DB tables having foreign key constraints referring to non-indexed columns
The product defect QCCR1L45264 has reported that in PPM DB schema there are some tables with foreign key constraints, and no indexes defined on the referenced columns. The ticket is available on the SSO portal via the following URL:
Tables FM_FORECAST_ACTUAL_LINES and FM_FINANCIAL_LINE_CELLS are 2 of the tables from this defect.
QCCR1L45264 has been resolved in version 9.14.0006, and if you are running on a previous release, you can upgrade to 9.14.0006 or later release, which adds a new set of indexes on the foreign key columns.