Performance Tuning in Informatica

We use Informatica for data integration and the choice is primarily due to its efficiency. But sometimes due to some wrong decisions we aggravate the situation through wrong decisions.

Below are some of the things which I came across my project so that Efficiency can be improved, leading to good efficient mapping.

1. Remove unused ports in the source qualifer.

2. If you use aggregator transformation, enable sorted input option.

Two ways are there,

2.1. Keep a sorter transformation before aggregator, sort the key columns alone.

2.2. You can avoid sorter by using order by clause in the SQL override option of source qualifier.

3. Enable persistent cache of the lookup tables that are to be used in the lookup transformation, if the same tables are          being used in the upcoming mappings.

4. Use Parameter files for relational connections in the source and targets by specifying parameter variables like                    $Source and $Target. Specify the path of the files in UNIX server in the workflow properties. It eliminates the need          setting connections manually and it becomes tedious when you move the mappings and sessions across the various        environments like QA,PROD and DEV.

5. Restore the tracing levels to Normal in the tranformations, so that no data is collected at repository after testing.

6. Enable version controlling so that we control the changes that are being done. In case of Unix servers create unix            groups so that only users of that particular group have access.