You can configure partitioning for Teradata mappings that you run in the native environment. When a mapping that is enabled for partitioning contains a Teradata data object as a target, the Data Integration Service can use multiple threads to write to the target.
You can configure dynamic partitioning for Teradata Parallel Transporter API data objects. You can configure the partition information so that the Data Integration Service determines the number of partitions to create at run time.
To enable partitioning, administrators and developers perform the following tasks:
Administrators set maximum parallelism for the Data Integration Service to a value greater than 1 in the Administrator tool.
Maximum parallelism determines the maximum number of parallel threads that process a single pipeline stage. Administrators increase the
property value based on the number of CPUs available on the nodes where mappings run.
Developers can set a maximum parallelism value for a mapping in the Developer tool.
By default, the
property for each mapping is set to Auto. Each mapping uses the maximum parallelism value defined for the Data Integration Service.
Developers can change the maximum parallelism value in the mapping run-time properties to define a maximum value for a particular mapping. When maximum parallelism is set to different integer values for the Data Integration Service and the mapping, the Data Integration Service uses the minimum value of the two.
When you create a Teradata write data object, ensure that the