Component family |
Databases/DB Generic | |
Basic settings |
Property type |
Either Built-in or Repository. Since version 5.6, both the Built-In mode and the Repository mode are available in any of the Talend solutions. |
|
|
Built-in: No property data stored centrally. |
|
|
Repository: Select the repository file in which the properties are stored. The fields that follow are completed automatically using the data retrieved. |
|
Datasource |
Name of the data source defined via the database connection configuration wizard. |
|
Username and Password |
DB user authentication data. To enter the password, click the [...] button next to the password field, and then in the pop-up dialog box enter the password between double quotes and click OK to save the settings. |
|
Schema and Edit Schema |
A schema is a row description. It defines the number of fields (columns) 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. |
|
|
Built-In: You create and store the schema locally for this component only. Related topic: see Talend Studio User Guide. |
|
|
Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs. Related topic: see Talend Studio User Guide. |
Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
| ||
|
Table Name |
Name of the source table where changes made to data should be captured. |
|
Query type |
Either Built-in or Repository. Since version 5.6, both the Built-In mode and the Repository mode are available in any of the Talend solutions. |
|
|
Built-in: Fill in manually the query statement or build it graphically using SQLBuilder |
|
|
Repository: Select the relevant query stored in the Repository. The Query field gets accordingly filled in. |
|
Query |
Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. |
Die on error |
This check box is cleared by default, meaning to skip the row on error and to complete the process for error-free rows. If needed, you can retrieve the rows on error via a Row > Rejects link. | |
Advanced settings |
Additional JDBC parameters |
Specify additional connection properties for the database connection you are creating. NoteYou can set the encoding parameters through this field. |
Propagate QUERY's recordset |
Select this check box to insert the result of the query into a COLUMN of the current flow. Select this column from the use column list. | |
|
Use PreparedStatement |
Select this check box if you want to query the database using a PreparedStatement. In the Set PreparedStatement Parameter table, define the parameters represented by "?" in the SQL instruction of the Query field in the Basic Settings tab. Parameter Index: Enter the parameter position in the SQL instruction. Parameter Type: Enter the parameter type. Parameter Value: Enter the parameter value.
NoteThis option is very useful if you need to execute the same query several times. Performance levels are increased |
|
Commit every |
Number of rows to be completed before committing batches of rows together into the DB. This option ensures transaction quality (but not rollback) and above all better performance on executions. |
|
tStatCatcher Statistics |
Select this check box to collect log data at the component level. |
Global Variables |
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 further information about variables, see Talend Studio User Guide. | |
Usage |
This component offers the flexibility of the DB query and covers all possible SQL queries. Note that the relevant DBRow component should be preferred according to your DBMSs. Most of the DBMSs have their specific DBRow components. | |
Log4j |
If you are using a subscription-based version of the Studio, the activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User Guide. 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. |