Uma Bojja

 Profile Answers by Uma Bojja 

• Jun 16th, 2006

 

Constraint based load ordering

example:

Table 1---Master

Tabke 2---Detail

If the data in table1 is dependent on the data in table2 then table2 should be loaded first.In such cases  to control the load order of the tables we need some conditional loading which is nothing but constraint based load

In Informatica this feature is implemented  by just one check box at the session level.

Thanks

Uma

Motilal

• Jun 30th, 2006

 

Target load order comes in the designer property..Click mappings tab in designer and then target load plan.It will show all the target load groups in the particular mapping. You specify the order there the server will loadto the target accordingly.

A target load group is a set of source-source qulifier-transformations and target.

Where as constraint based loading is a session proerty. Here the multiple targets must be generated from one source qualifier. The target tables must posess primary/foreign key relationships. So that, the server loads according to the key relation irrespective of the Target load order plan.

Sivasankar

• Jul 6th, 2006

 

If you have only one source, it?s loading into multiple target means you have to use Constraint based loading. But the target tables should have key relationships between them.

If you have multiple source qualifiers, it has to be loaded into multiple target, you have to use Target load order.

kjs

• Oct 13th, 2006

 

Constraint based loading : If your mapping contains single pipeline(flow) with morethan one target (If target tables contain Master -Child relationship) , you need to use constraint based load in session level.

Target Load plan : If your mapping contains multipe pipeline(flow)  (specify execution order one by one.example pipeline 1 need to execute first then pipeline 2 then pipeline 3) this is purly based on pipeline dependency