Skip to main content

Dynamic Look up in Informatica

By
We will be having a dilemma that when should we go for  dynamic lookup so let us discuss about that first. When we create a lookup on a target table and we are sure that there will be no duplicates coming from source data on PK Combination we go for a static cache lookup. But when there are duplicates coming from source end and we need to pick a latest value from the set then we go for dynamic look up. let me brief you with an example data

Name   Location
AAA    IND
BBB     USA
CCC     EUR
AAA    EUR

suppose we have data in the above following manner and only latest records should be pulled into the target so that the target data should look like in the following manner

Name Location
AAA  EUR
BBB   USA
CCC   EUR

When we select dynamic cache in look up properties a new column named as NewLookupRow gets added in ports section of look up.




Then we need select Insert else Update and Update else insert option.

The Newlook up row when the value returns as 0 means there is no change in data
The Newlook up row when the value returns as 1 means row should be inserted
The Newlook up row when the value returns as 2 means row should be updated

In the flow at router juncture we can give NewLookupRow=1 as insert condition and NewLookupRow=2 for updating records

Hope this article helps you in understanding Dynamic look up concept




Comments

  1. TejutejuJune 25, 2018 at 12:44 AM

    It is nice blog Thank you provide important information and i am searching for same information to save my time Informatica Online Course Bangalore

    ReplyDelete

Post a Comment

Popular posts from this blog

Comparing Objects in Informatica

By
We might face a scenario where there may be difference between PRODUCTION v/s SIT version of code or any environment or between different folders in same environment. In here we go for comparison of objects we can compare between mappings,sessions,workflows In Designer it would be present under "Mappings" tab we can find "Compare" option. In workflow manger under "Tasks & Workfows" tab we can find "Compare" option for tasks and workflows comparison respectively. However the easiest and probably the best practice would be by doing using Repository Manager.In Repository Manager under "Edit" tab we can find "Compare" option. The advantage of using Repository manager it compares all the objects at one go i.e. workflow,session and mapping. Hence reducing the effort of individually checking the mapping and session separately. Once we select the folder and corresponding workflow we Can click compare for checking out ...
11 comments
Read more

Finding Duplicate records and Deleting Duplicate records in TERADATA

By Anonymous
Requirement: Finding duplicates and removing duplicate records by retaining original record in TERADATA Suppose I am working in an office and My boss told me to enter the details of a person who entered in to office. I have below table structure. Create Table DUP_EXAMPLE ( PERSON_NAME VARCHAR2(50), PERSON_AGE INTEGER, ADDRS VARCHAR2(150), PURPOSE VARCHAR2(250), ENTERED_DATE DATE ) If a person enters more than once then I have to insert his details more than once. First time, I inserted below records. INSERT INTO DUP_EXAMPLE VALUES('Krishna reddy','25','BANGALORE','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Anirudh Allika','25','HYDERABAD','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Ashok Vunnam','25','CHENNAI','INTERVIEW',TO_DATE('01-JAN-2014',...
2 comments
Read more

Updating Target Table in Informatica

By Anonymous
Generally, in every project we will see at least one requirement to update target based on some conditions. Case1: When we have primary key defined on table in Database Case2:   When we do not have primary key defined on table in Database Case3: When we want to update target based on non-primary key field. Let’s discuss it in detail. Case1: When we have primary key defined on table in Database After creating table in DB, import table as target along with primary key constraints. After done with importing, we can check the primary key details by editing target in target definition. In this case, we can use update strategy to update target table. Suppose, we have a table called RETURN_CD and primary key ROW_WID defined on that table. Now, we can update target table using update strategy based on primary key. In mapping, we should connect primary key port and the ports which we want to update in target table. Please check the below screenshot. And ...
Post a Comment
Read more