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

Full Pushdown Optimization

Full Pushdown Optimization

When the Data Integration Service applies full pushdown optimization, it pushes all the transformation logic in the mapping to the source database. You can configure full pushdown in the mapping run-time properties.
Full pushdown optimization is ideal when the source and target are in the same database or when transformations such as Aggregator and Filter transformations are processed in the source database and reduce the amount of data moved. For example, if a mapping contains a Teradata source and Teradata target, configure full pushdown optimization to push all the transformation logic for processing from a Teradata source database to a Teradata target database.
When you configure a mapping with an Update Strategy transformation for full pushdown, you must determine pushdown compatibility for the mapping.
The Data Integration Service can pushdown a mapping with an Update Strategy transformation in the following scenarios:
  • If the target transformation connected to the Update Strategy transformation receives multiple rows that do not have the same key.
  • If the target transformation connected to the Update Strategy transformation receives multiple rows with the same key that can be reordered.
The Data Integration Service cannot pushdown a mapping with an Update Strategy transformation in the following scenario:
  • If the target transformation connected to the Update Strategy transformation receives multiple rows with the same key that cannot be reordered.
You can also use a pushdown compatibility parameter in the mapping. You can use the following parameter values:
  • noMultipleRowsWithSameKeyOnTarget
  • reorderAllowedForMultipleRowsWithSameKey
  • reorderNotAllowedForRowsWithSameKey
The Data Integration Service can use full pushdown optimization for the following sources:
  • Amazon Redshift
  • Greenplum
  • IBM DB2
  • Microsoft SQL Server
  • Netezza
  • Oracle
  • SAP HANA
  • Snowflake
  • Teradata

0 COMMENTS

We’d like to hear from you!