Limits on Update Jobs
When the Update operator executes, the actual session limit is determined by the first limiting factor that is encountered.
The Update operator requires one Teradata Database load slot when the job uses the traditional MultiLoad protocol.
The number of concurrent load slots is, however, configurable in the Teradata Database environment using the same MaxLoadTasks field control used by FastLoad, FastExport, and MultiLoad. For example, one Teradata PT Update job equates to one MultiLoad .IMPORT step in a MultiLoad job in the count for MaxLoadTasks.
When the job uses the extended MultiLoad protocol, the Update operator requires one Teradata Database load slot if the configurable Teradata Database control field, MLOADXUtilityLimits, is set to FALSE.
If MLOADXUtilityLimits is set to TRUE, the Update operator requires one Teradata Database extended MultiLoad protocol slot when the job uses the extended MultiLoad protocol.
The number of concurrent extended MultiLoad protocol slots is, however, configurable in the Teradata Database environment using the MaxMLOADXTasks field control. The number of concurrent extended MultiLoad protocol slots counts when the MLOADXUtilityLimits field control is set to TRUE.
Sample scenarios include:
For more information, see “DBS Control Utilities” in Utilities: Volume 1 (A-K).