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?
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
Start —-> Session 1 ——> Session 2 ——-> Session 3
Reason to avoid this approach: Higher efforts and Code implementation is more
Mapping 1: Session 1
A –> B
B –> C
C –> D
Target load plan option need to place in Mapping Designer
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.