Table of Contents

Search

  1. Preface
  2. Understanding Pipeline Partitioning
  3. Partition Points
  4. Partition Types
  5. Pushdown Optimization
  6. Pushdown Optimization and Transformations
  7. Real-time Processing
  8. Commit Points
  9. Row Error Logging
  10. Workflow Recovery
  11. Stopping and Aborting
  12. Concurrent Workflows
  13. Grid Processing
  14. Load Balancer
  15. Workflow Variables
  16. Parameters and Variables in Sessions
  17. Parameter Files
  18. FastExport
  19. External Loading
  20. FTP
  21. Session Caches
  22. Incremental Aggregation
  23. Session Log Interface
  24. Understanding Buffer Memory
  25. High Precision Data

Advanced Workflow Guide

Advanced Workflow Guide

Joiner Transformation

Joiner Transformation

Push a Joiner transformation to the database to optimize the use of indexes and statistics from the database.
The following table shows the pushdown types for each database to which you can push the Joiner transformation:
Database
Pushdown Type
Amazon Redshift
Source-side, Full
Greenplum
Source-side, Full
IBM DB2
Source-side, Full
Microsoft SQL Server
Source-side, Full
Netezza
Source-side, Full
Oracle
Source-side, Full
PostgreSQL
Source-side, Full
SAP HANA
Source-side, Target-side, Full
Snowflake
Source-side, Full
Sybase ASE
Source-side, Full
Teradata
Source-side, Full
Vertica
Source-side, Full
Microsoft Azure SQL Data Warehouse
Source-side, Full
The Integration Service processes the Joiner transformation if any of the following conditions are true:
  • The Integration Service cannot push the master and detail pipelines of the Joiner transformation to the database.
  • The join condition is based on a column with a binary datatype.
  • The incoming groups of a Joiner transformation originate from databases on different relational database management systems.
  • The session is configured to mark all source rows as updates and configured for pushdown optimization to Teradata.
  • The transformation is configured with an outer join, and the master or detail source is a multi-table join. The Integration Service cannot generate SQL to represent an outer join combined with a multi-table join.
  • The transformation is configured with a full outer join and configured for pushdown optimization to Sybase.
  • The Integration Service created a view or sequence based on a transformation in the master branch, and the master and detail branches do not come from the same database.
  • The transformation is pushed to Microsoft SQL Server, Sybase, or Teradata and is downstream from a Sorter transformation, which is downstream from an Aggregator transformation.
  • The transformation is downstream from a Sorter transformation and is pushed to Microsoft SQL Server, Sybase, or Teradata, and the master and detail tables stem from the same Source Qualifier transformation instance.


Updated November 14, 2019