August 17, 2023

tELTTeradataOutput – Docs for ESB 5.x



tELTTeradataOutput properties

The three ELT Teradata components are closely related, in terms of their operating
conditions. These components should be used to handle Teradata DB schemas to generate
Insert statements, including clauses, which are to be executed in the DB output table

Component family




Carries out the action on the table specified and inserts the data
according to the output schema defined the ELT Mapper.


Executes the SQL Insert, Update and Delete statement to the
Teradata database.

Basic settings


Use tCreate Table as substitute for this

Action on data

On the data of the table defined, you can perform the following

Insert: Add new entries to the
table. If duplicates are found, Job stops.

Update: Updates entries in the

Delete: Deletes the entries which
correspond to the entry flow.


Schema and Edit

A schema is a row description. It defines the number of fields to be processed and passed on
to the next component. The schema is either Built-In or
stored remotely in the Repository.

Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.

Click Edit schema to make changes to the schema. If the
current schema is of the Repository type, three options are

  • View schema: choose this option to view the
    schema only.

  • Change to built-in property: choose this option
    to change the schema to Built-in for local

  • Update repository connection: choose this option to change
    the schema stored in the repository and decide whether to propagate the changes to
    all the Jobs upon completion. If you just want to propagate the changes to the
    current Job, you can select No upon completion and
    choose this schema metadata again in the [Repository



Built-in: The schema is created
and stored locally for this component only. Related topic: see
Talend Studio User



Repository: The schema already
exists and is stored in the Repository, hence can be reused. Related
topic: see Talend Studio User


Where clauses for (for UPDATE and DELETE

Enter a clause to filter the data to be updated or deleted during
the update or delete operations.


Default Table Name

Enter a default name for the table, between double quotation


Use different table name

Select this check box to enter a different output table name,
between double quotation marks, in the Table
field which appears.

Advanced settings

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at a
Job level as well as at component level.

Global Variables

NB_LINE: the number of rows read by an input component or
transferred to an output component. This is an After variable and it returns an

NB_LINE_INSERTED: the number of rows inserted. This is an
After variable and it returns an integer.

ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl +
to access the variable list and choose the variable to use from it.

For further information about variables, see Talend Studio
User Guide.


tELTTeradataOutput is to be used
along with the tELTTeradataMap.
Note that the Output link to be used with these components must
correspond strictly to the syntax of the table name.


Note that the ELT components do not handle actual data flow
but only schema information.


The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User

For more information on the log4j logging levels, see the Apache documentation at


Due to license incompatibility, one or more JARs required to use this component are not
provided. You can install the missing JARs for this particular component by clicking the
Install button on the Component tab view. You can also find out and add all missing JARs easily on
the Modules tab in the Integration perspective
of your studio. For details, see
or the section describing how to configure the Studio in the Talend Installation and Upgrade

Related scenarios

For use cases in relation with tELTTeradataOutput,
see tELTMysqlMap scenarios:

Document get from Talend
Thank you for watching.
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x