Skip to main content

Teradata components

tTeradataClose Closes the transaction committed in the connected DB.
tTeradataCommit Commits in one go, using a unique connection, a global transaction instead of doing that on every row or every batch and thus provides gain in performance.
tTeradataConfiguration Defines a connection to Teradata and enables the reuse of the connection configuration in the same Job.
tTeradataConnection Opens a connection to the specified database that can then be reused in the subsequent subJob or subJobs.
tTeradataFastExport Exports data batches from a Teradata table to a customer system or to a smaller database.
tTeradataFastLoad Executes a database query according to a strict order which must be the same as the one in the schema.
tTeradataFastLoadUtility Executes a database query according to a strict order which must be the same as the one in the schema.
tTeradataInput Executes a DB query with a strictly defined order which must correspond to the schema definition.
tTeradataLookupInput Executes a database query with a strictly defined order which must correspond to the schema definition.
tTeradataMultiLoad Executes a database query according to a strict order which must be the same as the one in the schema.
tTeradataOutput Executes the action defined on the table and/or on the data contained in the table, based on the flow incoming from the preceding component in the job.
tTeradataRollback Cancels the transaction commit in the Teradata database.
tTeradataRow Acts on the actual DB structure or on the data (although without handling data).
tTeradataTPTExec Offers high performance in inserting data from an existing file to a table in a Teradata database.
tTeradataTPTUtility Writes the incoming data to a file and then loads the data from the file to a Teradata database.
tTeradataTPump Inserts, updates, or deletes data in the Teradata database with the TPump loading utility which allows near-real-time data to be achieved in the data warehouse.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!