July 30, 2023

tDBSQLRow – Docs for ESB 7.x


Acts on the actual DB structure or on the data (although without handling data)
depending on the nature of the query and the database. The SQLBuilder tool helps you write
easily your SQL statements.

tDBSQLRow is the generic
component for database query. 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 does not provide
output. For performance reasons, specific DB component should always
be preferred to the generic component.

To use this component, relevant DBMSs’ ODBC drivers should be
installed and the corresponding ODBC connections should be
configured via the database connection configuration

tDBSQLRow Standard properties

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

The Standard
tDBSQLRow component belongs to the Databases family.

The component in this framework is available in all Talend

Basic settings

Property type

Either Built-in or


Built-in: No property data stored


Repository: Select the repository
file in which the properties are stored. The fields that follow are
completed automatically using the data retrieved.


Name of the data source defined via the database connection
configuration wizard.

Username and

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

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. If the current schema is of the Repository type, three options are available:

  • 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

Name of the source table where changes made to data should be

Query type

Either Built-in or


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.


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

Advanced settings

Additional JDBC parameters

Specify additional connection properties for the database
connection you are creating.


You 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

Parameter Value: Enter the
parameter value.


This 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

Global Variables

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 +
to access the variable list and choose the variable to use from it.

For further information about variables, see
Talend Studio

User Guide.


Usage rule

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

Resetting a DB auto-increment

This scenario describes a single component Job which aims at re-initializing the DB
auto-increment to 1. This job has no output and is generally to be used before running a


As a prerequisite of this Job, the relevant DBMS’s ODBC
driver must have been installed and the corresponding ODBC connection must have
been configured.


  1. Drag and drop a tDBSQLRow component from the
    Palette to the design workspace.


  2. Double-click tDBSQLRow to open its Basic settings view.


  3. Select Repository in the Property Type list as the ODBC connection has been
    configured and saved in the Repository. The follow-up fields gets filled in

    For more information on storing DB connections in the Repository, see

    Talend Studio User Guide
  4. The Schema is built-in for this Job and it
    does not really matter in this example as the action is made on the table
    auto-increment and not on data.
  5. The Query type is also built-in. Click on the
    […] button next to the Query statement box to launch the SQLbuilder editor,
    or else type in directly in the statement box:

    Alter table <TableName> auto_increment = 1
  6. Press Ctrl+S to save the Job and F6 to run.

    The database autoincrement is reset to 1.

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