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

Active and Idle Databases

Active and Idle Databases

During pushdown optimization, the Integration Service pushes the transformation logic to one database, which is called the active database. A database that does not process transformation logic is called an idle database. For example, a mapping contains two sources that are joined by a Joiner transformation. If the session is configured for source-side pushdown optimization, the Integration Service pushes the Joiner transformation logic to the source in the detail pipeline, which is the active database. The source in the master pipeline is the idle database because it does not process transformation logic.
The Integration Service uses the following criteria to determine which database is active or idle:
  • When using full pushdown optimization, the target database is active and the source database is idle.
  • In sessions that contain a Lookup transformation, the source or target database is active, and the lookup database is idle.
  • In sessions that contain a Joiner transformation, the source in the detail pipeline is active, and the source in the master pipeline is idle.
  • In sessions that contain a Union transformation, the source in the first input group is active. The sources in other input groups are idle.
To push transformation logic to an active database, the database user account of the active database must be able to read from the idle databases.


Updated June 25, 2020