
APPENDIX 147
For tables on dierent database servers or dierent database types, additional components
and actions will need to be added from the source DB to the new components (see Figure
A.3).
Figure A.3 – One Database Table to Multiple Database Tables
Each individual mapping is created separately using the DB Conversion sub-window.
Multiple Source Tables to Multiple Destination Tables
As long as tables have a one-to-one or one-to-many relationship, the mappings are created
with multiple DB-to-DB pairings (see Figure A.4) or by combining the components by
server using the patterns above.
Keeping each component separate will not aect the execution of a task in any way; it will
only aect the complexity of the task diagram inside TaskBuilder.
Figure A.4 – Multiple Source Tables to Multiple Destination Tables
Note
Actions that use multiple tables on the same server can be linked to the same com-
ponent assuming that the username/password combination used to access that
server has the appropriate rights for all tables in the task that start or end on that
component. If this is not the case, separate DB components must be created for each
username/password combination.
Commentaires sur ces manuels