Differences between OLTP, OLAP, ODS, DWH and DSS systems (Infographic)
March 26, 2016
Testing Roles and Responsibilities
Roles and Responsibilities of an ETL Testing Professional
April 10, 2016
Show all

Why we go for Target Load Plan Option in Informatica?

Why this option?

To perform dependency load between tables

Scenario to implement this?

A, B, C, D are the table’s, If the requirement is to load table A data to B, B table data to C  and C table data to D, then this option will be useful. In this Scenario every table is dependent to it’s predecessor’s data load completion.

How we will implement this requirement?

Option 1:

Build each data load logic as an individual, Like

A             –>          B             — Mapping 1      — Session 1

B             –>          C             — Mapping 2      — Session 2

C             –>          D             — Mapping 3      — Session 3

Workflow Creation:

Start —-> Session 1 ——> Session 2 ——-> Session 3

Reason to avoid this approach: Higher efforts and Code implementation is more

Option 2:

Mapping 1: Session 1

A             –>          B

B             –>          C

C             –>          D

Target load plan option need to place in Mapping Designer

Target load plan Option


It display’s popup to arrange table loading, Change the order by clicking on the up and down arrow buttons.Table Order Change










Workflow Creation:

Start —-> Session 1

How integration services execute this logic?

The Integration Service reads sources in a target load order group concurrently, and it processes target load order groups sequentially.