Table of Contents

Search

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

Developer Mapping Guide

Developer Mapping Guide

Semi-Join Optimization Rules and Guidelines

Semi-Join Optimization Rules and Guidelines

The Data Integration Service can apply semi-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 joiner transformation cannot perform a full outer join.
  • The detail pipeline must originate from a relational source.
  • The join condition must be a valid sort-merge-join condition. That is, each clause must be an equality of one master port and one detail port. If there are multiple clauses, they must be joined by AND.
  • If the mapping does not use 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.

0 COMMENTS

We’d like to hear from you!