Performance Considerations - MultiLoad

Teradata® MultiLoad Reference - 20.00

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
MultiLoad
Release Number
20.00
Published
October 2023
Language
English (United States)
Last Update
2024-03-18
dita:mapPath
lji1691576359330.ditamap
dita:ditavalPath
kju1619195148891.ditaval
dita:id
sga1478609868891
Product Category
Teradata Tools and Utilities

The majority of client processing during a Teradata MultiLoad job occurs when it is processing its input rows. The most efficient means of sending the row to the database would be a bulk move of the input row to the output row.

However, there are many cases where fields need to be evaluated and field data may need to be individually moved from the input to the output row. Note, however, that performance is affected whenever a field needs to be evaluated or individually moved.

The need for moving individual field data from the input to the output row occurs for any of the following scenarios:
  • DROP syntax on FIELD statements
  • FILLER fields
  • Concatenated fields
  • Complex layout (first field is variable-length field, redefinition of field positions)

Variable length fields, NULLIF in the layout, and APPLY WHERE clauses might require additional CPU consumption.