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

Pushdown Compatibility

Pushdown Compatibility

To push a transformation with multiple connections to a database, the connections must be pushdown compatible. Connections are pushdown compatible if they connect to databases on the same database management system and the Integration Service can identify the database tables that the connections access.
The following transformations can have multiple connections:
  • Joiner.
    The Joiner transformation can join data from multiple source connections.
  • Union.
    The Union transformation can merge data from multiple source connections.
  • Lookup.
    The connection for the Lookup transformation can differ from the source connection.
  • Target.
    The target connection can differ from the source connection.
Each connection object is pushdown compatible with itself. If you configure a session to use the same connection object for the source and target connections, the Integration Service can push the transformation logic to the source or target database.
Some relational connections are pushdown compatible if they are of the same database type, have the same database user name and password, and have certain identical properties.
The following table lists the connection properties that must be identical for each database type:
Database Type
Connection Properties that Must be Identical
IBM DB2
Connect string
Code page
Connection environment SQL
Transaction environment SQL
Greenplum
Code page
Connect string
Connection environment SQL
Transaction environment SQL
Microsoft SQL Server
Code page
Server name
Domain name
Use trusted connection
Connection environment SQL
Transaction environment SQL
Oracle
Connect string
Code page
Connection environment SQL
Transaction environment SQL
Sybase ASE
Code page
Server name
Connection environment SQL
Transaction environment SQL
Teradata
Code page
Data source name
Connection environment SQL
Transaction environment SQL
Vertica
Code page
Connect string
Connection environment SQL
Transaction environment SQL
Microsoft Azure SQL Data Warehouse
Code page
Server name
Domain name
Use trusted connection
Connection environment SQL
Transaction environment SQL
The Integration Service performs a case-sensitive string comparison to verify that connection properties are identical.
Netezza databases in the same relational database management system are pushdown incompatible. A Netezza database is only pushdown compatible with itself.
If the connection properties in Pushdown Compatibility for connections of the same database type are identical, but the database user names and passwords differ, you might still be able to make the connections pushdown compatible.


Updated August 27, 2020