Writer partitions process SQL inserts only. They do not process SQL updates or deletes.

You can use writer partitioning for sequential file and VSAM targets, including VSAM ESDS, KSDS, and RRDS data sets.

Writer partitions must use pass-through partitioning.

You must use PWX NRDB Batch application connections to the target.

If resources on the target system are constrained, consider using offload processing in combination with writer partitioning to improve session performance.

The performance of partitioned sessions depends on the PowerCenter Integration Service machine, network speed, and target system. If a session has high CPU usage, use a PowerCenter Integration Service machine with multiple CPUs. Also ensure that the target system and network speed are fast enough to keep up with partitioned session processing. Otherwise, bottlenecks might occur.

If you want to use a single target connection and the same session overrides for all partitions, set the

PWX Partition Strategy

session property to

Single Connection

. With this setting, you can specify the session overrides for the first partition only, and the PowerCenter Integration Service uses these overrides for all other writer partitions.

If you specify a SQL statement in the

Pre SQL

property for a bulk data movement session that uses a PWX NRDB Batch connection and writer partitioning, the session executes the SQL statement in each partition. The session fails if you specify a SQL statement such as CREATEFILE that can run only once for the session. The session executes the statement in the first partition and then fails when trying to execute it again in another partition. Either enter a SQL statement that can run once in each partition, or do not specify the

Pre SQL

attribute for writer partitions.