Each operator used in a single-step job, or in a job step, will attempt to simultaneously log on to one database session for each AMP configured on the database system. However, this may not be optimal for every job. For some jobs, the default parallelism may be excessive. In other cases, there may not be enough available AMPs to provide the sessions necessary to run the job efficiently. Teradata PT provides the following attributes to optimize session usage for the five operators that support session limits.
- MaxSessions determines the maximum number of sessions an operator can use.
- MinSessions determines the minimum number of sessions that must be available in order for the job to run.