Teradata Parallel Data Pump

Chapter 1: Overview
Teradata TPump Utility
In contrast, Teradata TPump can always be stopped and all of its locks dropped with no ill
effect.
Resource Consumption
MultiLoad is designed for the highest possible throughput, and uses any database and host
resources that help to achieve this capability. There is no way to reduce MultiLoad's resource
consumption—even if a longer run time for the job is acceptable. Teradata TPump, however,
has a built-in resource governing facility.
This allows the operator to specify how many updates occur (the statement rate) minute by
minute, and then change the statement rate, while the job continues to run. Thus, this facility
can be used to increase the statement rate during windows when Teradata TPump is running
by itself, but then decrease the statement rate later on, if users log on for ad hoc query access.
Teradata TPump Support Environment
The data-handling functionality of Teradata TPump is enhanced by the Teradata TPump
support environment. In addition to coordinating activities involved in Teradata TPump
tasks, it provides facilities for managing file acquisition, conditional processing, and
performing certain Data Manipulation Language (DML) and Data Definition Language
(DDL) activities on Teradata Database. The Teradata TPump support environment enables an
additional level of user control over Teradata TPump.
For more information, see “Teradata TPump Support Environment” on page 37.
What it Does
Within a single invocation of Teradata TPump, one or more distinct Teradata TPump tasks
can be executed in series with any Teradata TPump support commands.
The Teradata TPump task provides the acquisition of data from client files for application to
target tables through INSERT, UPDATE, or DELETE statements that specify the full primary
index. Data is retrieved from the client, and sent as transaction rows to Teradata Database,
which are immediately applied to the various target tables.
Each Teradata TPump task can acquire data from one or many client files with similar or
different layouts. From each source record, one or more INSERT, UPDATE, or DELETE
statements can be generated and directed to any target table.
The following concepts may improve how Teradata TPump is understood.
• The language of Teradata TPump commands and statements is used to describe the task
which needs to be accomplished.
• Teradata TPump examines all commands and statements for a task, from the BEGIN
LOAD command through the END LOAD command, before actually executing the task.
• After all commands and statements involved in a given task have been processed and
validated by Teradata TPump, the Teradata TPump task is executed as described in this
and subsequent chapters.
Teradata Parallel Data Pump Reference 17