Table of Contents

Search

  1. Preface
  2. Mappings
  3. Mapplets
  4. Mapping Parameters
  5. Mapping Outputs
  6. Generate a Mapping from an SQL Query
  7. Dynamic Mappings
  8. How to Develop and Run a Dynamic Mapping
  9. Dynamic Mapping Use Cases
  10. Mapping Administration
  11. Export to PowerCenter
  12. Import From PowerCenter
  13. Performance Tuning
  14. Pushdown Optimization
  15. Partitioned Mappings
  16. Developer Tool Naming Conventions

Developer Mapping Guide

Developer Mapping Guide

Dataship-Join Optimization Rules and Guidelines

Dataship-Join Optimization Rules and Guidelines

The Data Integration Service can apply dataship-join optimization to a Joiner transformation if the transformation meets the following requirements:
  • The join type must be normal, master outer, or detail outer.
  • The detail pipeline must originate from a relational source.
  • If the mapping uses target-based commits, the Joiner transformation scope must be All Input.
  • The master and detail pipelines cannot share any transformation.
  • The mapping cannot contain a branch between the detail source and the Joiner transformation.
  • The Data Integration Service fails to apply the dataship-join optimization method if the database which contains the detail side of the join is an IBM DB2 database that does not support Unicode encoding.

0 COMMENTS

We’d like to hear from you!