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

Rules and Guidelines for Relational Source Partitions

Rules and Guidelines for Relational Source Partitions

Consider the following rules and guidelines when you enable partitioning for a mapping that reads from a relational source:
  • The Data Integration Service uses one thread to read the source, but can use multiple threads for the remaining mapping pipeline stages in the following situations:
    • The mapping reads from a relational source other than DB2 for LUW or Oracle.
    • The mapping uses a JDBC or ODBC connection to read from a DB2 for LUW or Oracle source.
    • The mapping pushes transformation logic to the source database.
    • You use the simple query in the Read transformation to select the ports to sort by or to configure a user-defined join.
    • You use the advanced query in the Read transformation to create a custom SQL query.
  • If you use the simple query in the Read transformation to create hints, select distinct values, or enter a source filter, the Data Integration Service can use multiple threads to read the source. The Data Integration Service adds the hints, distinct values, or source filter to the SQL query generated for each partition.

0 COMMENTS

We’d like to hear from you!