Table of Contents

Search

  1. Preface
  2. Understanding Pipeline Partitioning
  3. Partition Points
  4. Partition Types
  5. Pushdown Optimization
  6. Pushdown Optimization 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
  26. POWERCENTERHELP

Advanced Workflow Guide

Advanced Workflow Guide

Rules and Guidelines for Source Database Partitioning

Rules and Guidelines for Source Database Partitioning

Use the following rules and guidelines when you use the database partitioning partition type with relational sources:
  • You cannot use database partitioning when you configure the session to use source-based or user-defined commits, constraint-based loading, or workflow recovery.
  • When you configure a source qualifier for database partitioning, the Integration Service reverts to pass-through partitioning under the following circumstances:
    • The database table is stored on one database partition.
    • You run the session in debug mode.
    • You specify database partitioning for a session with one partition.
    • You use pushdown optimization. Pushdown optimization works with the other partition types.
  • When you create an SQL override to read database tables and you set database partitioning, the Integration Service reverts to pass-through partitioning and writes a message to the session log.
  • If you create a user-defined join, the Integration Service adds the join to the SQL statements it generates for each partition.
  • If you create a source filter, the Integration Service adds it to the WHERE clause in the SQL query for each partition.


Updated July 04, 2018