Siebel Performance Tuning Guide > Tuning Siebel EIM > Troubleshooting Siebel EIM Performance >

Dropping Indexes in Initial Runs of Siebel EIM

This topic is part of Troubleshooting Siebel EIM Performance.

Typically, the Siebel EIM initial load is a very database-intensive process. Each row that is inserted into the base table requires modifications on the data page and the index pages of all the affected indexes. However, most of these indexes are never used during a Siebel EIM run. Index maintenance is very time-consuming for most database managers and must be avoided as much as possible.

Therefore, the goal is to determine any indexes that are unnecessary for Siebel EIM and that can be dropped for the durations of the Siebel EIM run. You can create these indexes later in batch mode by using parallel execution strategies available for the respective database platform. Using this approach can save a significant amount of time.

NOTE:  Under normal operations, using parallel execution strategies is not recommended.

• Target Table Indexing Strategy. For a target base table (such as S_ORG_EXT) you only need to use the Primary Index (Px, for example P1), and the Unique Indexes (Ux, for example U1), and then drop the remaining indexes for the duration of the Siebel EIM import. Past experience has determined that the Fx and Mx indexes can be dropped after an extensive SQL analysis of sample Siebel EIM runs.
• Nontarget Table Indexing Strategy. For child tables (such as S_ADDR_ORG) you only need to use the Primary Index (Px), the Unique Indexes (Ux), and the Foreign Key Indexes (needed for setting primary foreign keys in the parent table). Past experience has determined that the Fx and Mx indexes can be dropped after an extensive SQL analysis of sample Siebel EIM runs.

NOTE:  Always perform testing when dropping indexes (or adding indexes) to make sure that expected results are achieved.