July 31, 2023

tJDBCRow – Docs for ESB Jdbc 7.x


Acts on the actual DB structure or on the data (although without handling data)
using the SQLBuilder tool to write easily your SQL statements.

tJDBCRow is the component for any type database using a
JDBC API. It executes the SQL query stated onto the specified database. The row suffix
means the component implements a flow in the job design although it doesn’t provide

tJDBCRow Standard properties

These properties are used to configure tJDBCRow running in the Standard Job framework.

The Standard
tJDBCRow component belongs to the Databases family.

The component in this framework is available in all Talend

Note: This component is a specific version of a dynamic database
connector. The properties related to database settings vary depending on your database
type selection. For more information about dynamic database connectors, see Dynamic database components.

Basic settings


Select a type of database from the list and click

Property Type

Select the way the connection details
will be set.

  • Built-In: The connection details will be set
    locally for this component. You need to specify the values for all
    related connection properties manually.

  • Repository: The connection details stored
    centrally in Repository > Metadata will be reused by this component. You need to click
    the […] button next to it and in the pop-up
    Repository Content dialog box, select the
    connection details to be reused, and all related connection
    properties will be automatically filled in.

This property is not available when other connection component is selected
from the Connection Component drop-down list.

Connection Component

Select the component that opens the database connection to be reused by this


The JDBC URL of the database to be used. For
example, the JDBC URL for the Amazon Redshift database is jdbc:redshift://endpoint:port/database.


Complete this table to load the driver JARs needed. To do
this, click the [+] button under the table to add
as many rows as needed, each row for a driver JAR, then select the cell and click the
[…] button at the right side of the cell to
open the Module dialog box from which you can select the driver JAR
to be used. For example, the driver jar RedshiftJDBC41- for the Redshift database.

For more information, see Importing a database driver.

Driver Class

Enter the class name for the specified driver between double
quotation marks. For example, for the RedshiftJDBC41- driver, the name to be entered is

Use Id and Password

The database 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. When you create a Spark
Job, avoid the reserved word line when naming the

  • Built-In: You create and store the schema locally for this component

  • Repository: You have already created the schema and stored it in the
    Repository. You can reuse it in various projects and Job designs.

Click Edit
to make changes to the schema.

Note: If you
make changes, the schema automatically becomes built-in.
  • 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 changes.

  • 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 Content

Table Name

The name of the table to be processed.

Query Type and Query

Specify the database query statement paying particularly attention to the
properly sequence of the fields which must correspond to the schema definition.

  • Built-In: Fill in the query statement in the
    Query field manually or click the
    […] button next to the Query field
    to build the statement graphically using the SQLBuilder.

  • Repository: Select the relevant query stored in the
    Repository by clicking the […] button next to it and in the
    pop-up Repository Content dialog box, select the query to be
    used, and the Query field will be automatically filled

Guess Query

Click this button to generate query in the Query field based on
the defined table and schema.

Specify a data source alias

Select this check box and in the
Data source alias field displayed, specify the alias of
a data source created on Talend Runtime side to use
the shared connection pool defined in the data source configuration. This option
works only when you deploy and run your Job in Talend Runtime.

If you use the component’s own DB configuration, your data source
connection will be closed at the end of the component. To prevent this from
happening, use a shared DB connection with the data source alias specified.

This property is not available when other connection component is selected from
the Connection Component drop-down list.

Die on error

Select the check box to stop the execution of the Job when an error

Clear the check box to skip any rows on error and complete the
process for error-free rows.

When errors are skipped, you can collect the rows on error
using a Row > Reject connection.

Advanced settings

Propagate QUERY’s recordset

Select this check box to propagate the result of the query to the output flow. From the
use column list displayed, you need to select a column into
which the query result will be inserted.

This option allows the component to have a different schema from that of the preceding
component. Moreover, the column that holds the query’s recordset should be set to the
Object type and this component is usually followed by a
tParseRecordSet component.

Use PreparedStatement

Select this check box if you want to query the database using a prepared statement. In
the Set PreparedStatement Parameters table displayed, specify the
value for each parameter represented by a question mark ? in the
SQL statement defined in the Query field.

  • Parameter Index: the position of the parameter in the SQL

  • Parameter Type: the data type of the parameter.

  • Parameter Value: the value of the parameter.

For a related use case of this property, see Using PreparedStatement objects to query data.

Commit every

Specify the number of rows to be processed before committing
batches of rows together into the database.

This option ensures transaction quality (but not rollback) and, above all, better
performance at executions.

tStatCatcher Statistics

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

Global Variables


The error message generated by the component when an error occurs. This is an After
variable and it returns a string.


The query statement being processed. This is a Flow variable and it returns a


Usage rule

This component offers the flexibility of the DB query for any
database using a JDBC connection and covers all possible SQL queries.

Dynamic settings

Click the [+] button to add a row in the table
and fill the Code field with a context
variable to choose your database connection dynamically from multiple
connections planned in your Job. This feature is useful when you need to
access database tables having the same data structure but in different
databases, especially when you are working in an environment where you
cannot change your Job settings, for example, when your Job has to be
deployed and executed independent of Talend Studio.

For examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic
and context variables, see Talend Studio
User Guide.

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