About Increasing the Number of Sessions - Teradata Data Mover

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
kmo1482331935137.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

Data Mover provides the ability to independently specify the number of source and target sessions that a job uses when transferring data. When creating jobs through the command-line interface, the number of sessions used can be specified with the source_sessions and target_sessions parameters when using the create or move command.

Specifying a higher number of sessions can improve individual job performance, although specifying too many sessions can lead to performance degradation. The optimal number of sessions varies depending on the environment and the utility being used. Consult Teradata Archive/Recovery Utility Reference, Teradata Parallel Transporter Reference, and Teradata JDBC Driver User Guide for details.

If you do not provide a value for source and/or target sessions, Data Mover will dynamically determine the number of sessions; this determination is based on multiple factors, including number of AMPs, size of objects being moved, and so forth. This dynamic value is a good starting point, but advanced users may find more ideal settings to use for each situation.