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

Router Transformation

Router Transformation

The following table shows the pushdown types for each database to which you can push the Router 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
ODBC
Source-side, Full
Microsoft Azure SQL Data Warehouse
Source-side, Full
You can use source-side pushdown when all output groups merge into one transformation that can be pushed to the source database.
The Integration Service processes the Router transformation if the router expression cannot be pushed to the database. For example, if the expression contains an operator that cannot be pushed to the database, the Integration Service does not push the expression to the database.


Updated June 25, 2020