anilkumar

• Feb 19th, 2006

 

1) Limit base tables and columns to be processed by using : only base Tables,ignore base Tables,only base Columns,ignore base Columns.

2) Always delete batches from EIM tables upon completion. Leaving old batches in the EIM table wastes space and can adversely affect performance. For other suggestions on working with batches.

3) Run independent EIM jobs in parallel. Two or more EIM processes can be started simultaneously by using the Siebel Server Manager.

4) Trace Flag Settings, using Synonyms, primary key only Parameters

Limiting the Number of Records and Rows for Merge Processes.

like this many techniques are there which will optimize the EIM process  

Lal

• Jun 25th, 2006

 

Apart from that, you can use index.

Even using batch ranges ( eg. 100 to 200 ) will also increase the performance as it reduces the startup overheads.

Pavan

• Aug 20th, 2006

 

Hi, Even removing ( drop index) the index keys is also a crucial phenomenon here, because it reduces the additional work of EIM, and also we have to take care , the SQL trace flag is not set to 8 the job parameters of EIM srr job, for fast processing, or else it slows the processing as it saves a huge log file everytime, thk u Pavan

pdmaheshpd

 Profile Answers by pdmaheshpd 

• Sep 24th, 2008

 

1) Limit base tables and columns
2) Run independent EIM jobs in parallel.

joe_mec

 Profile Answers by joe_mec 

• Jul 1st, 2010

 

Drop index only during initial loads.
Also you can remove Database Triggers for better performance.
Pls dont forget to create index and enable Database Triggers after the load is complete.
 

Regards
Joe