July 30, 2023

tSQLDWHCommit – Docs for ESB 7.x


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

If you need to commit each statement as an individual transaction, you have to use the
Auto Commit function available in the connection component.

tSQLDWHCommit Standard properties

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

The Standard
tSQLDWHCommit component belongs to two families: Cloud and Databases.

The component in this framework is available in all Talend

Basic settings

Component List

Select the tSQLDWHConnection 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.

Note that if you want to use a Row > Main connection to link tSQLDWHCommit 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 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 more commonly used with other Azure SQL Data Warehouse components,
especially with the tSQLDWHConnection and
tSQLDWHRollback 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
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.


Note that some features that are supported by
other databases are not supported by Azure SQL Data Warehouse. For more information,
see Unsupported table features.

Related scenario

No scenario is available for this component yet.

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