Constraint Based Loading is used to load data first in parent target table and then child target table, we can specify constraint based loading option in session properties under config tab.
Integration service process record row by row basis, for every row generated by source the integration service first load data into primary key table then foreign key table.
It is helpful to normalize data from de-normalized source data.
important points:
1. constraint based loading option only for insert.
2. can not update or delete rows with this option.
3. it can be implemented only when target having primary and foreign key relationship.
4.target table must be in the same target connection group.
For update and delete using constraint based load, informatica provides option to insert, updates and deletes in target table in other words complete constraint based loading can be enabled by specify custom properties "FullCBLOSupport=Yes" under config tab of session.
We can specify this property in integration service which make it applicable for all session and workflows.
If we are using complete constraint based loading mapping should not contain active transformation which can change Row ID value (Agg, Joiner,Normalizer,Rank,sorter).
Using Row id we can update,delete and insert data into target.
Integration service process record row by row basis, for every row generated by source the integration service first load data into primary key table then foreign key table.
It is helpful to normalize data from de-normalized source data.
important points:
1. constraint based loading option only for insert.
2. can not update or delete rows with this option.
3. it can be implemented only when target having primary and foreign key relationship.
4.target table must be in the same target connection group.
For update and delete using constraint based load, informatica provides option to insert, updates and deletes in target table in other words complete constraint based loading can be enabled by specify custom properties "FullCBLOSupport=Yes" under config tab of session.
We can specify this property in integration service which make it applicable for all session and workflows.
If we are using complete constraint based loading mapping should not contain active transformation which can change Row ID value (Agg, Joiner,Normalizer,Rank,sorter).
Using Row id we can update,delete and insert data into target.
1 comment:
Useful Information :
Looking for the Best [url= Digital Marketing in Vijayawada ][/url] , We provide training on live projects, internship, Flexible Classes, Free Demo @ praiseads.com
Post a Comment