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
defined.
Component family |
ELT/Map/Teradata |
|
Function |
Carries out the action on the table specified and inserts the data |
|
Purpose |
Executes the SQL Insert, Update and Delete statement to the |
|
Basic settings Warning
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
Update: Updates entries in the
Delete: Deletes the entries which |
|
Schema and Edit |
A schema is a row description. It defines the number of fields to be processed and passed on Since version 5.6, both the Built-In mode and the Repository mode are Click Edit schema to make changes to the schema. If the
|
|
|
Built-in: The schema is created |
|
|
Repository: The schema already |
|
Where clauses for (for UPDATE and DELETE |
Enter a clause to filter the data to be updated or deleted during |
|
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, |
Advanced settings |
tStatCatcher Statistics |
Select this check box to gather the Job processing metadata at a |
Global Variables |
NB_LINE: the number of rows read by an input component or
NB_LINE_INSERTED: the number of rows inserted. This is an ERROR_MESSAGE: the error message generated by the A Flow variable functions during the execution of a component while an After variable To fill up a field or expression with a variable, press Ctrl + For further information about variables, see Talend Studio |
|
Usage |
tELTTeradataOutput is to be used NoteNote that the ELT components do not handle actual data flow |
|
Log4j |
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 http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html. |
|
Limitation |
Due to license incompatibility, one or more JARs required to use this component are not |
For use cases in relation with tELTTeradataOutput,
see tELTMysqlMap scenarios: