July 31, 2023

tJDBCSP – Docs for ESB Jdbc 7.x


Centralizes multiple or complex queries in a database in order to call them

tJDBCSP Standard properties

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

The Standard
tJDBCSP 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.

SP Name

The name of the stored procedure.

Is function

Select this check box if the stored procedure is a function and a value will be
returned from the stored procedure. With this check box selected, you need to select the
column in which the returned value will be saved from the Return result
drop-down list.

Set SP Parameters

Specify the parameters for the stored procedure by clicking the
[+] button to add as many rows as needed, each row for a
parameter, and setting the following value for each parameter.

  • Schema Column: The column that holds the parameter

  • Parameter Type: The type of the parameter.

    • IN: The input parameter.

    • OUT: The output parameter/return value.

    • IN OUT: The combination of input and output parameters.
      It means the parameter can be passed to the stored procedure, modified by the
      procedure, and returned with a new value.

    • RECORDSET: The input parameter will be returned as a set
      of values, rather than a single value.

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

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.

Advanced settings

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.


Usage rule

This component is used as intermediary component. It can be
used as start component but only input parameters are thus allowed.

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.


The Stored Procedures syntax should match the Database syntax.

Related scenario

For related scenarios, see:

Check as well Inserting data in mother/daughter tables if you want to analyze a set of records from a database table or DB query and return
single records.

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