July 30, 2023

tVectorWiseCommit – Docs for ESB 7.x


Commits a global transaction in one go using a single connection instead of doing
so on every row or every batch. This provides a gain in performance

tVectorWiseCommit validates the data processed in a Job into the connected

tVectorWiseCommit Standard properties

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

The Standard
tVectorWiseCommit 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

Component list

Select the tVectorWiseConnection
component from the list if more than one connection is 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.


If you want to use a Row

connection to link tVectorWiseCommit 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

tStatCatcher Statistics

Select this check box to collect log data at the component


Usage rule

This component is more commonly used with other tVectorWise*
components, especially with the tVectorWiseConnection and tVectorWiseRollback 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.

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

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.

Related scenario

For a tVectorWiseCommit related scenario, see Inserting data in mother/daughter tables.

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