August 15, 2023

tJDBCCommit – Docs for ESB 6.x

tJDBCCommit

Commits in one go a global transaction instead of doing that on every row or every
batch and thus provides gain in performance.

tJDBCCommit validates the data
processed through the Job into the connected DB.

tJDBCCommit Standard properties

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

The Standard
tJDBCCommit component belongs to the Databases family.

The component in this framework is generally available.

Basic settings

Component list

Select the tJDBCConnection
component in the list if more than one connection are planned for
the current Job.

Close Connection

This check box is selected by default. It allows you to close the
database connection once the commit is done. Clear this check box to
continue to use the selected connection once the component has
performed its task.

Warning:

If you want to use a Row
>

Main
connection to link tJDBCCommit to your Job, your data will be
committed row by row. In this case, do not select the
Close connection check
box or your connection will be closed before the end of your
first row commit.

Advanced settings

tStat
Catcher
Statistics

Select this check box to collect log data at the component
level.

Usage

Usage rule

This component is more commonly used with other tJDBC* components,
especially with the tJDBCConnection
and tJDBCRollback
components.

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
.

Once a dynamic parameter is defined, the Component List box in the Basic
settings
view becomes unusable.

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

Related scenario

For tJDBCCommit related scenario, see Scenario: Inserting data in mother/daughter tables.


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