Teradata standalone load and unload utilities are fast, reliable tools that help to export large amounts of data from Teradata databases and load session target files into Teradata databases. Use a standalone load or unload utility when PowerCenter sessions extract or load large amounts of data. Standalone load and unload utilities are faster than Teradata relational connections because they load or extract data directly from a file or pipe rather than run SQL commands to load or extract the data.

1. 3White Paper|Working with Informatica-Teradata Parallel Transporter
2. Teradata standalone Load and Unload Utilities
Teradata standalone load and unload utilities are fast, reliable tools that help to
export large amounts of data from Teradata databases and load session target files
into Teradata databases. Use a standalone load or unload utility when PowerCenter
sessions extract or load large amounts of data. Standalone load and unload utilities
are faster than Teradata relational connections because they load or extract data
directly from a file or pipe rather than run SQL commands to load or extract the data.
PowerCenter works with the following Teradata standalone load and unload utilities:
2.1. Teradata FastLoad
x Teradata FastLoad is a command-line utility that quickly loads large amounts
of data to empty tables in a Teradata database. Use FastLoad for a high-
volume initial load or for high-volume truncate and reload operations.
FastLoad is the fastest load utility, but it has the following limitations:
x FastLoad uses multiple sessions to load data, but it can load data to only one
table in a Teradata database per job.
x It locks tables while loading data, preventing others and other instances of
FastLoad from accessing the tables during data loading.
x FastLoad only works with empty tables with no secondary indexes.
x It can only insert data.
2.2. Teradata MultiLoad
Teradata MultiLoad is a command-driven utility for fast, high-volume
maintenance on multiple tables and views of a Teradata database. Each
MultiLoad instance can perform multiple data insert, update, and delete
operations on up to five different tables or views. MultiLoad optimizes operations
that rapidly acquire, process, and apply data to Teradata tables. Use MultiLoad
for large volume, incremental data loads.
2.2.1.MultiLoad has the following advantages:
x MultiLoad is very fast. It can process millions of rows in a few minutes.
x MultiLoad supports inserts, updates, upserts, deletes, and data-driven
operations in PowerCenter.
x We can use variables and embed conditional logic into MultiLoad control
files.
x MultiLoad supports sophisticated error recovery. It allows load jobs to be
restarted without having to redo all of the prior work.

2. 4White Paper|Working with Informatica-Teradata Parallel Transporter
2.2.2. MultiLoad has the following limitations:
x MultiLoad is designed for the highest possible throughput, so it can be very
resource intensive.
x It locks tables while loading data, preventing others and other instances of
MultiLoad from accessing the tables during data loading.
x Because of its “phased” nature, there are potentially inconvenient windows
of time when MultiLoad cannot be stopped without losing access to target
tables.
2.3. Teradata TPump
Teradata TPump is a highly parallel utility that can continuously move data from
data sources into Teradata tables without locking the affected table. TPump
supports inserts, updates, deletes, and data-driver updates. TPump acquires row
hash locks on a database table instead of table-level locks, so multiple TPump
instances can load data simultaneously to the same table. TPump is often used to
“trickle-load” a database table. Use TPump for low volume, online data loads.
2.3.1.TPump has the following advantages:
x TPump can refresh database tables in near real-time.
x TPump continuously loads data into Teradata tables without locking the
affected tables, so users can run queries when TPump is running.
x TPump is less resource-intensive than MultiLoad because it does not write to
temporary tables.
x Users can control the rate at which statements are sent to the Teradata
database, limiting resource consumption.
x It supports parallel processing.
x TPump can always be stopped and all of its locks dropped with no effect.
x TPump is not as fast as the other standalone loaders for large volume loads
because it changes the same data block multiple times.
2.4. Teradata FastExport
Teradata FastExport is a command-driven utility that uses multiple sessions to
quickly transfer large amounts of data from Teradata sources to PowerCenter.
Use FastExport to quickly extract data from Teradata sources.
2.4.1. FastExport has the following advantages:
x It is faster than Teradata relational connections when extracting large
amounts of data.
x FastExport can be run in streaming mode, which avoids the need to stage
the data file.

3. 5White Paper|Working with Informatica-Teradata Parallel Transporter
x We can encrypt the data transfer between FastExport and the Teradata
server.
x FastExport is available for sources and pipeline lookups.
When we create a FastExport connection, verify the settings of the following
connection attributes:
x Data encryption.
Enable this attribute to encrypt the data transfer between FastExport and
the Teradata server so that unauthorized users cannot access the data being
transferred across the network.
x Fractional seconds.
This attribute specifies the precision of the decimal portion of timestamp
data. To avoid session failure or possible data corruption, make sure this
value matches the timestamp precision of the column in the Teradata
database. For date column filed selects from Teradata to Informatica we
need to match the Teradata date format with Informatica date format
To use FastExport in a session, configure the mapping to extract from a Teradata
source, configure the session to read from FastExport instead of a relational
database, and select the FastExport connection for the session. When a session
transfers data between Teradata and PowerCenter, the following files are
created:
x A staging file or pipe.
PowerCenter creates a staging file or named pipe for data transfer based on
how we configure the connection. Named pipes are generally faster than
staging files because data is transferred as soon as it appears in the pipe. If
we use a staging file, data is not transferred until all data appears in the file.
x A control file.
PowerCenter generates a control file that contains instructions for loading or
extracting data. PowerCenter creates the control file based on the loader or
FastExport attributes we configure for the connection and the session.
x A log file.
The load or unload utility creates a log file and writes error messages to it.
The PowerCenter session log indicates whether the session ran successfully,
but does not contain load or unload utility error messages. Use the log file to
debug problems that occur during data loading or extraction.