# tSingleStoreCommit

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

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

## tSingleStoreCommit Standard properties

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

The Standard tSingleStoreCommit component belongs to the Databases family.

The component in this framework is available in all subscription-based Talend products.

## Basic settings

| Properties | Description |
| --- | --- |
| Database | Select the desired database type from the list and click<br>Apply. |
| Component list | Select the component that opens the database connection to be reused by this<br>component. |
| Close Connection | Select this check box to close the database connection once the component has performed<br>its task.<br><br>Clear this check box to continue to use the selected connection once the component has<br>performed its task.<br><br>If this component is linked to your Job via a Row &gt; Main connection, your data will be committed row by row. In this case, do not<br>select the Close connection check box or your<br>connection will be closed before the end of the first row commit. |

## Advanced settings

| Properties | Description |
| --- | --- |
| tStatCatcher Statistics | Select this checkbox to gather the Job processing metadata at the Job level<br>as well as at each component level. |

## Global Variables

| Variables | Description |
| --- | --- |
| ERROR\_MESSAGE | The error message generated by the component when an error<br>occurs. This is an After variable and it returns a string. |

## Usage

| Usage guidance | Description |
| --- | --- |
| **Usage rule** | This component is more commonly used with other tSingleStore\*<br>components, especially with the tSingleStoreConnection and tSingleStoreRollback components. |
| Dynamic settings | Click the [+] button to add a row in the table<br>and fill the Code field with a context<br>variable to choose your database connection dynamically from multiple<br>connections planned in your Job. This feature is useful when you need to<br>access database tables having the same data structure but in different<br>databases, especially when you are working in an environment where you<br>cannot change your Job settings, for example, when your Job has to be<br>deployed and executed independent of Talend Studio.<br><br>For examples on using dynamic parameters, see [Reading data from databases through<br>context-based dynamic connections](https://help.qlik.com/talend/r/en-US/8.0/components/defining-context-groups/reading-data-from-databases-through-context-based-dynamic-connections) and [Reading data from different MySQL databases<br>using dynamically loaded connection parameters](https://help.qlik.com/talend/r/en-US/8.0/components/context/reading-data-from-different-mysql-databases-using-dynamically-loaded-connection-parameters). For more information on<br>Dynamic settings and context variables, see<br>[Dynamic schema](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/dynamic-schema) and [Creating a context group and define context<br>variables in it](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/creating-context-group-and-define-context-variables-in-it). |