Rules and Guidelines for Dynamic Partitioning

Use the following rules and guidelines with dynamic partitioning:

1. Dynamic partitioning uses the same connection for each partition.
2. You cannot use dynamic partitioning with XML sources and targets.
3. You cannot use dynamic partitioning with the Debugger.
4. Sessions that use SFTP fail if you enable dynamic partitioning.
5. When you set dynamic partitioning to a value other than disabled, and you manually partition the session on the Mapping tab, you invalidate the session.
6. The session fails if you use a parameter other than $DynamicPartitionCount to set the number of partitions.

The following dynamic partitioning configurations cause a session to run with one partition:

• You override the default cache directory for an Aggregator, Joiner, Lookup, or Rank transformation. The Integration Service partitions a transformation cache directory when the default is $PMCacheDir.
• You override the Sorter transformation default work directory. The Integration Service partitions the Sorter transformation work directory when the default is $PMTempDir.
• You use an open-ended range of numbers or date keys with a key range partition type.
• You use datatypes other than numbers or dates as keys in key range partitioning.
• You use key range relational target partitioning.
• You create a user-defined SQL statement or a user-defined source filter.
• You set dynamic partitioning to the number of nodes in the grid, and the session does not run on a grid.
• You use pass-through relational source partitioning.
• You use dynamic partitioning with an Application Source Qualifier.
• You use SDK or PowerConnect sources and targets with dynamic partitioning.