Professional Documents
Culture Documents
A user might have come across an ETL scenario, where you need to update a huge table with few
records and occasional inserts. The straightforward approach of using LookUp transformation to identify
the Inserts, Update and Update Strategy to do the Insert or Update may not be right for this particular
scenario, mainly because of the LookUp transformation may not perform better and start degrading as
the lookup table size increases.
In this article let's talk about a design, which can take care of the scenario we just spoke.
The Theory
When you configure an Informatica PowerCenter session, you have several options for handling
database operations such as insert, update, delete.
During session configuration, you can select a single database operation for all rows using the Treat
Source Rows As setting from the 'Properties' tab of the session.
Once you determine how to treat all rows in the session, you can also set options for individual rows,
which gives additional control over how each row behaves. Define these options in the Transformations
view on the Mapping tab of the session properties.
Now we understand the properties we need to use for our design implementation.
We can create the mapping just like an 'INSERT' only mapping, without LookUp, Update Strategy
Transformation. During the session configuration lets set up the session properties such that the session
will have the capability to both insert and update.
Now lets set the properties for the target table as shown below. Choose the
properties Insert and Update else Insert.
That's all we need to set up the session for update and insert without update strategy.