Wednesday, June 13, 2007

Optimizing Enterprise Integration Manager

Optimizing Enterprise Integration Manager

Use below process to capture/find out where problem exist.
  1. Turn on 'Level 8' EIM logging.
  2. Turn on SQL Profiler for the run.
  3. Run an EIM batch.
  4. Load the EIM log into Excel. Sort the log on execution time to find what is the longest execution time. Find this event In the unsorted EIM log.
  5. Load the SQL Profile trace into Excel. Sort on the longest duration, then on reads. These queries should match those in the EIM log.
  6. Review the execution plans. Isolate the problem. Determine how the problem can be fixed. Keep in mind that a combination of solutions may bring about the most improvement.

Optimization TIPs.

Here are the few factors to optimize EIM performance.

The loading strategy: This is the one of the most important factor to load data in EIM tables. Before inserting data into EIM tables you should analyze what data is being change and how date will be updated. What base tables are updated. It’s better to separate data into batches before loading into EIM tables. Suppose you have data to insert and you have executed EIM process with default parameters. When EIM executed its check whether records exit or not if not insertion will be performed otherwise existing record will be update and this is more costly operations. Think and organize when you have heavy data to process. Divide data into batches based on operation (insert, update, delete & merge).

Index:
Turn off optimizer hints: Performance can be optimized but turning off hint optimizer. Testing should tell you if this strategy is effective or not.

Syntax:
USEINDEXHINTS,FALSE
USEESSENTIALHINTS,FALSE

Avoid updates: Ensure configuration (.IFB) file that no updates are performed (if not required).

Syntax:
INSERT ROWS=S_CONTACT,TRUE
UPDATE ROWS=S_CONTACT,FALSE

Fragmentation: During database load; data can be fragmented resulting poor performance because of more data pages must be read by SQL. To avoid fragmentation try to use index options FILLFACTOR and PAD_INDEX reduce fragmentation. The FILLFACTOR option reserves space on each leaf page of an index, while the PAD_INDEX option reserves space in the intermediate index pages.

Note: I have written above after reading technical notes from www.siebelonmicrosoft.com and EIM Administration Guide from Siebel bookshelf.


# posted by Rajesh Kumar : 6:12 AM
Comments: Post a Comment



<< Home

This page is powered by Blogger. Isn't yours?