Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Order of execution in mapping

Status
Not open for further replies.

bsellick

Programmer
Jul 26, 2001
24
0
0
CA
I have the following situation in mapping (Informatica v6):

Source -> SQ -> Expression -> Target

Source -> SQ -> Expression -> Target

Source -> SQ -> Expression -> Target

Source -> SQ -> Expression -> Target

Each source is different but the target is the same table (just renamed logically each time).

The first question I have is: when this mapping is run, does each stream run sequentially starting at the first stream listed and working down or do all streams run simultaneously?

Based on the answer for above - if I checked on the "target truncate" field for stream #1, can I be sure that I'll always truncate the target before records are inserted from other streams?
 
bsellick

I am fairly new to Informatica, so bear with me.

I believe the "Target Truncate" option is set in a Workflow, not a Mapping. Therefore, it doesn't matter what order the Mapping is executed.
 
Oh, yes. Sorry.

That option is turned on in the session object.

However, it has only been turned on for the first target table - the one in the very first processing stream shown in the mapping (which may have a logical name of TABLE1 but the underlying physical table name would be the same for all targets).

 
OK

I'm pretty sure the target table will be truncated by the Workflow before any of the Mapping ("the session")is executed.
 
Also you can use Target Load Order in the mapping - Mappings Target Load Plan if you want to control not having them sequential within the mapping. It goes by source qualifier.
 
yes pbackstrom is correct. You can define you own sequence in mapping (in Informatica Designer) using Mapping --> Target Load option. Here you can set the sequence.

While Truncate target will work only once at starting of the work flow. So dont worry about that. It will not truncate everytime.
 
Generally speaking, INFA good practice is NOT to create mappings with unrelated dataflows. Create a mapping for each dataflow and sessions on each mapping.
This will allow you maximum control if you put them sequentially in a workflow...

Ties Blom
Information analyst
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top