Skip to main content

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 if we edit update strategy in mapping, we can “update strategy expression” property. When we want to update target, we should set it to DD_UPDATE.

When you are using update strategy, we should “check” update as update property in target properties in session.





Case2:  When we do not have primary key defined on table in Database
If we do not have primary key defined on table in database, after importing target in to informatica target definition, edit the target and set primary key in informatica level as per your requirement.
When we edit target, we can see KEY TYPE as NOT A KEY. So, we should change it to primary key.


Once we set primary key in informatica level, follow the same process to update target table as we saw it in CASE1. Even if we create primary key in informatica level then also target table will be updated correctly.

Case3: When we want to update target based on non-primary key field.
In the above two cases, we have seen how we can update target using primary keys. Now, let’s discuss how can we update target using non-primary key fields.
After done with creation of mapping, if we edit target, we can see Target Update Override property.


And we can write update query like below.

UPDATE TARGET_TABLE_NAME
SET TARGET_COLUMN1 = :TU.INCOMING_PORT1,
    [Additional update columns]
WHERE TARGET_COLUMN = :TU.INCOMING_PORT
AND   [Additional conditions]

Or we can click on “generate SQL” and then we can modify query as per requirement.

If you have any questions, please feel free to write to kkrishnareddychp@gmail.com

Comments

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

Target Load Type - Normal or Bulk in Session Properties

By
We can see the Target load type ( Normal or Bulk) property in session under Mapping tab and we will go for Bulk to improve the performance of session to load large amount of data. SQL loader utility will be used for Bulk load and it will not create any database logs(redolog and undolog), it directly writes to data file.Transaction can not be rolled back as we don't have database logs.However,Bulk loading is very as compared to Normal loading. In target if you are using Primary Key or Primary Index or any constraints you can't use Bulk mode. We can see this property in the below snap shot.
Post a Comment
Read more