tSQLTemplateMerge Standard properties
These properties are used to configure tSQLTemplateMerge running in the Standard Job framework.
The Standard tSQLTemplateMerge component belongs to the ELT family.
The component in this framework is available in all Talend products.
Basic settings
Database Type |
Select the type of database you want to work on from the drop-down list. |
Component list |
Select the relevant DB connection component from the list if you use more than one connection in the current Job. |
Source table name |
Name of the database table holding the data you want to merge into the target table. |
Target table name |
Name of the table you want to merge data into. |
Schema and Edit schema |
This component involves two schemas: source schema and target schema. A schema is a row description, that is to say, it defines the number of fields to be processed and passed on to the next component. The schema is either built-in or remotely stored in the Repository. Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
|
|
Built-in: The schema is created and stored locally for this component only. For more information about a component schema in its Basic settings tab, see Basic settings tab. |
|
Repository: The schema already exists and is stored in the Repository, hence can be reused. For more information about a component schema in its Basic settings tab, see Basic settings tab. |
Merge ON |
Specify the target and source columns you want to use as the primary keys. |
Use UPDATE (WHEN MATCHED) |
Select this check box to update existing records. With the check box selected, the UPDATE Columns table appears, allowing you to define the columns in which records are to be updated. |
Specify additional output columns |
Select this check box to update records in additional columns other than those listed in the UPDATE Columns table. With this check box selected, the Additional UPDATE Columns table appears, allowing you to specify additional columns. |
Specify UPDATE WHERE clause |
Select this check box and type in a WHERE clause in the WHERE clause field to filter data during the update operation. Information noteNote:
This option may not work with certain database versions, including Oracle 9i. |
Use INSERT (WHEN MATCHED) |
Select this check box to insert new records. With the check box selected, the INSERT Columns table appears, allowing you to specify the columns to be involved in the insert operation. |
Specify additional output columns |
Select this check box to insert records to additional columns other than those listed in the INSERT Columns table. With this check box selected, the Additional INSERT Columns table appears, allowing you to specify additional columns. |
Specify INSERT WHERE clause |
Select this check box and type in a WHERE clause in the WHERE clause field to filter data during the insert operation. Information noteNote:
This option may not work with certain database versions, including Oracle 9i. |
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
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 integer. NB_LINE_MERGED: the number of rows merged. This is an After variable and it returns an integer. QUERY: the query statement being processed. This is a Flow variable and it returns a string. 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+Space to access the variable list and choose the variable to use from it. For more information about variables, see Using contexts and variables. |
Usage
Usage rule |
This component is used as an intermediate component with other relevant DB components, especially the DB connection and commit components. |
SQL Template |
SQL Template List |