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.