# tDatabricksServerlessSQLWarehouseOutput Standard properties

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

The Standard tDatabricksServerlessSQLWarehouseOutput component belongs to the Databases family.

This component supports Databricks serverless SQL warehouse by using Databricks JDBC connectivity.

The component in this framework is available in all Talend products.

Information noteNote: 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 [DB Generic components](https://help.qlik.com/talend/r/en-US/8.0/components/db-generic/db-generic-component).

## Basic settings

| Properties | Description |
| --- | --- |
| Database | Select the desired database type from the list and click<br>Apply. |
| Property Type | Select the way the connection details<br>will be set.<br><br><ul> <li> <p> <span>Built-In</span>: The connection details will be set                                locally for this component. You need to specify the values for all                                related connection properties manually.</p> </li> <li> <p> <span>Repository</span>: The connection details stored                                centrally in <span><span>Repository</span><abbr> &gt; </abbr><span>Metadata</span></span> will be reused by this component. </p> <p>You need to click                                the <span>[...]</span> button next to it and in the pop-up                                    <span>Repository Content</span> dialog box, select the                                connection details to be reused, and all related connection                                properties will be automatically filled in.</p> </li> </ul><br><br>This property is not available when other connection component is selected from<br>the Connection Component dropdown list. |
| Use an existing connection | Select this check box and in the Component<br>List drop-down list, select the desired connection component to<br>reuse the connection details you already defined. |
| Component list | Select the component that opens the database connection to be reused by this<br>component. |
| Schema and Edit schema | A schema is a row description. It defines the number of fields<br>(columns) to be processed and passed on to the next component. When you create a Spark<br>Job, avoid the reserved word line when naming the<br>fields.<br><br><ul> <li> <p> <span>Built-In</span>: You create and store the schema locally for this component                only.</p> </li> <li> <p> <span>Repository</span>: You have already created the schema and stored it in the                Repository. You can reuse it in various projects and Job designs.</p> </li> </ul><br><br>When the schema to be reused has default values that are<br>integers or functions, ensure that these default values are not enclosed within<br>quotation marks. If they are, you must remove the quotation marks manually.<br><br>For more information, see [Retrieving table schemas](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/retrieving-table-schemas?tocId=_C1~eFOlN~GM_JR2qkBYZg).<br><br>Click Edit schema to make changes to<br>the schema. If you make changes, the schema automatically becomes built-in.<br><br><ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                choose this option to change the schema stored in the repository and decide whether                to propagate the changes to all the Jobs upon completion.</p> <p>If you just want to                propagate the changes to the current Job, you can select <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul> |
| Guess Schema | Click this button to generate schema columns based on the settings of database table columns. |
| JDBC URL | The JDBC URL of the database to be used.<br><br>Information noteNote: There will be no migration operation for Databricks components when the<br>8.0.1-R2026-07 Talend Studio [Modules] monthly update or a later one delivered by Talend is installed. In this case, you may need to update the JDBC URL and other<br>related settings manually for existing Jobs to make sure the JDBC URL begins<br>with jdbc:databricks://. |
| **Drivers** | Complete this table to load the driver JARs needed. To do<br>this, click the [+] button under the table to add<br>as many rows as needed, each row for a driver JAR, then select the cell and click the<br>[...] button at the right side of the cell to<br>open the Module dialog box from which you can select the driver JAR<br>to be used. For example, the driver jar RedshiftJDBC41-1.1.13.1013.jar for the Redshift database.<br><br>For more information, see [Importing a database driver](https://help.qlik.com/talend/r/en-US/8.0/components/jdbc/importing-database-driver).<br><br>Information noteNote: There will be no migration operation for Databricks components when the<br>8.0.1-R2026-07 Talend Studio [Modules] monthly update or a later one delivered by Talend is installed. In this case, you may need to update the JDBC URL and other<br>related settings manually for existing Jobs to make sure the JDBC URL begins<br>with jdbc:databricks://. |
| **Driver Class** | Enter the class name for the specified driver between double<br>quotation marks. For example, for the RedshiftJDBC41-1.1.13.1013.jar driver, the name to be entered is<br>com.amazon.redshift.jdbc41.Driver.<br><br>Information noteNote: There will be no migration operation for Databricks components when the<br>8.0.1-R2026-07 Talend Studio [Modules] monthly update or a later one delivered by Talend is installed. In this case, you may need to update the JDBC URL and other<br>related settings manually for existing Jobs to make sure the JDBC URL begins<br>with jdbc:databricks://. |
| User Id and Password | The database user authentication data.<br><br>To enter the password, click the [...] button<br>next to the password field, enter the password in double quotes in the pop-up dialog box,<br>and click OK to save the settings. |
| Specify a data source alias | Select this checkbox and in the<br>Data source alias field displayed, specify the alias of<br>a data source created on Talend Runtime<br>side to use the shared connection pool defined in the data source configuration.<br>This option works only when you deploy and run your Job in Talend Runtime.<br><br>If you use the component's own DB configuration, your data source<br>connection will be closed at the end of the component. To prevent this from<br>happening, use a shared DB connection with the data source alias specified.<br><br>This property is not available when other connection component is selected from<br>the Connection Component dropdown list. |
| Table | Enter the name of the table into<br>which data will be written. |
| Data Action | Select an action to be performed on data of the<br>table defined.<br><br><ul> <li><p> <span>Insert</span>: Add            new entries to the table. If duplicates are found, the Job stops.</p></li> <li><p> <span>Update</span>:            Make changes to existing entries.</p></li> <li><p> <span>Insert or                update</span>: Insert a new record in the index pool. If the record with the            given reference already exists, an update would be made.</p></li> <li><p> <span>Update or                insert</span>: Update the record with the given reference. If the record does            not exist in the index pool, a new record would be inserted.</p></li> <li><p> <span>Delete</span>:            Remove entries corresponding to the input flow.</p></li> </ul> |
| Clear data in table | Select this checkbox to clear data in the table before performing the selected action. |
| Die on error | Select the checkbox to stop the execution of the Job when an error<br>occurs.<br><br>Clear the checkbox to skip any rows on error and complete the<br>process for error-free rows.<br><br>When errors are skipped, you can collect the rows on error<br>using a Row &gt; Reject connection. |

## 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. |
| Commit every | Specify the number of rows to be processed before committing<br>batches of rows together into the database. |
| Additional Columns | This option allows you to call SQL functions to perform actions on columns, which are<br>not insert, update or delete actions, or actions that require particular preprocessing.<br>It is not offered if you create (with or without drop) the database table.<br><br><ul> <li> <p> <span>Name</span>: The name of the schema column to be inserted, or the                name of the schema column used to replace an existing column.</p> </li> <li> <p> <span>SQL expression</span>: The SQL statement to be executed in order to                insert or replace relevant column.</p> </li> <li> <p> <span>Position</span>: Select <kbd>Before</kbd>,                  <kbd>After</kbd>, or <kbd>Replace</kbd> according to the                action to be performed on the reference column.</p> </li> <li> <p> <span>Reference column</span>: The name of the reference column that can                be used to locate the new column to be inserted or that will be replaced.</p> </li> </ul> |
| Use field options | Select this check box and in the Fields options table<br>displayed, select the check box for the corresponding column to customize a<br>request, particularly if multiple actions are being carried out on the<br>data.<br><br><ul> <li> <span>Key in update</span>: Select the check box for the                            corresponding column based on which data is updated.</li> <li> <span>Key in delete</span>: Select the check box for the                            corresponding column based on which data is deleted.</li> <li> <p> <span>Updatable</span>: Select the check box if data in the                                corresponding column can be updated.</p> </li> <li> <p> <span>Insertable</span>: Select the check box if data in                                the corresponding column can be inserted.</p> </li> </ul> |
| Debug query mode | Select this check box to display each step during processing entries<br>in a database. |
| Use batch | Select this check box to activate the batch mode for data<br>processing, and in the Batch Size field displayed, specify the<br>number of records to be processed in each batch. |
| Query timeout | Select this option to set a timeout period for queries or batch queries. The Job is terminated if a query times out. You can set the timeout period in seconds in the Timeout field. |

## 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. |
| NB\_LINE | The number of rows processed. This is an After variable and<br>it returns an integer. |
| NB\_LINE\_INSERTED | The number of rows inserted. This is an After variable and<br>it returns an integer. |
| NB\_LINE\_UPDATED | The number of rows updated. This is an After variable and it<br>returns an integer. |
| NB\_LINE\_DELETED | The number of rows deleted. This is an After variable and it<br>returns an integer. |
| NB\_LINE\_REJECTED | The number of rows rejected. This is an After variable and<br>it returns an integer. |
| QUERY | The query statement being processed. This is a Flow variable<br>and it returns a string. |

## Usage

| Usage guidance | Description |
| --- | --- |
| **Usage rule** | This component must be used as an output component. It supports writing data to Databricks serverless SQL warehouse tables and can create a reject flow using a Row &gt; Rejects link. |
| 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). |