Informatica Best Practices -2

The following design standards and best practices are recommended for applications that use Informatica for ETL activities:
Best Practices – Overall
1. Informatica server should be used only for batch transfer of data from source systems to destination databases. It should not be used for any real time transfer of data between systems.
2. All the sessions have to be re-executable i.e. if any session fails for any reason, the sessions must have the intelligence/capability to undo whatever is done and re-load from the scratch, once the session is re-run.
3. Pre-Session command scripts should be used for disabling constraints, building temporary tables, moving files etc. Post-Sessions scripts should be used for rebuilding indexes and dropping temporary tables.
4. Use the Source Qualifier Transformation, over the Filter Transformation to filter data for better performance when possible.

The following design standards and best practices are recommended for applications that use Informatica for ETL activities:

Best Practices – Overall

1. Informatica server should be used only for batch transfer of data from source systems to destination databases. It should not be used for any real time transfer of data between systems.

2. All the sessions have to be re-executable i.e. if any session fails for any reason, the sessions must have the intelligence/capability to undo whatever is done and re-load from the scratch, once the session is re-run.

3. Pre-Session command scripts should be used for disabling constraints, building temporary tables, moving files etc. Post-Sessions scripts should be used for rebuilding indexes and dropping temporary tables.

4. Use the Source Qualifier Transformation, over the Filter Transformation to filter data for better performance when possible.

Comments (0)

  • No comments yet.