tAzureSynapseConnection
tAzureSynapseConnection Standard properties
These properties are used to configure tAzureSynapseConnection running in the Standard Job framework.
The Standard tAzureSynapseConnection component belongs to two families: Cloud and Databases.
The component in this framework is available in all Talend products.
Basic settings
| Properties | Description |
|---|---|
|
Property Type |
Select the way the connection details will be set.
|
| JDBC Provider |
Select the provider of the JDBC driver to be used. |
| Host | Enter the IP address or the hostname of the database server or the Azure Synapse Analytics to be used. If the SQL Server Browser service is running on the machine where the server resides, you can connect to a named instance through a TCP dynamic port by providing the host name and the instance name in this field in the format of {host_name}\{instance_name}. In this case, you can leave the Port field empty. See SQL Server Browser service for related information. |
| Port | Enter the listening port number of the database server or the Azure Synapse Analytics to be used. If the SQL Server Browser service is running on the machine where the server resides, you can connect to a named instance through a TCP dynamic port by providing the host name and the instance name in the Host field and leave this field empty. See SQL Server Browser service for related information. |
| Schema | Enter the name of the Azure Synapse Analytics schema. |
| Database | Specify the name of the Azure Synapse Analytics to be used. |
| Username and Password | Enter the authentication data. To enter the password, click the [...] button next to the Password field, enter the password in double quotes in the pop-up dialog box, and then click OK. You can use Type 2 integrated authentication on Windows by adding integratedSecurity=true in the Additional JDBC Parameters field and leave these two fields empty. See section Connecting with integrated authentication On Windows at Building the connection URL for related information. |
| Additional JDBC Parameters |
Specify additional connection properties for the database connection you are creating. The properties are separated by semicolon and each property is a key-value pair. For example, encrypt=true;trustServerCertificate=false; hostNameInCertificate=*.database.windows.net;loginTimeout=30; for Azure SQL database connection. |
|
Use or register a shared DB Connection |
Select this checkbox to share your database connection or fetch a database connection shared by a parent or child Job, and in the Shared DB connection name field displayed, enter the name for the shared database connection. This allows you to share one single database connection (except the database schema setting) among several database connection components from different Job levels that can be either parent or child. This option is incompatible with the Use dynamic Job and Use an independent process to run subJob options of the tRunJob component. Using a shared connection together with a tRunJob component with either of these two options enabled will cause your Job to fail. This checkbox is not available when the Specify a data source alias checkbox is selected. |
|
Specify a data source alias |
Select this checkbox and in the Data source alias field displayed, specify the alias of a data source created on Talend Runtime side to use the shared connection pool defined in the data source configuration. This option works only when you deploy and run your Job in Talend Runtime. This checkbox is not available when the Use or register a shared DB Connection checkbox is selected. |
Advanced settings
| Properties | Description |
|---|---|
| Authenticate using Azure Active Directory | When selected, this option allows you to pick the authentication mode to use
from the Azure Active Directory authentication mode
dropdown list:
Read the Usage section of this document for information about Microsoft SQL Server/JDBC encryption requirements. |
|
Auto Commit |
Select this checkbox to commit any changes to the database automatically upon the transaction. With this checkbox selected, you cannot use the corresponding commit component to commit changes to the database; likewise, when using the corresponding commit component, this checkbox has to be cleared. By default, the auto commit function is disabled and changes must be committed explicitly using the corresponding commit component. Note that the auto commit function commits each SQL statement as a single transaction immediately after the statement is executed while the commit component does not commit only until all of the statements are executed. For this reason, if you need more room to manage your transactions in a Job, it is recommended to use the commit component. |
| Share identity insert in multi table | Select this checkbox to share IDENTITY_INSERT with multiple tables in one connection. |
|
tStatCatcher Statistics |
Select this checkbox to gather the Job processing metadata at the Job level as well as at each component level. |
Global Variables
| Variables | Description |
|---|---|
|
ERROR_MESSAGE |
The error message generated by the component when an error occurs. This is an After variable and it returns a string. |
Usage
| Usage guidance | Description |
|---|---|
| Usage rules | This component is more commonly used with other Azure Synapse Analytics
components and it opens a connection that can be reused by them. Information noteImportant: Microsoft SQL Server/JDBC encryption requirements
Starting with recent versions of the Microsoft SQL Server JDBC driver, TLS encryption is enabled by default (encrypt=true;trustServerCertificate=false). This enhances security, but if your SQL Server does not support encrypted connections or does not require clients to use TLS, you must set encrypt=false in the JDBC parameters of this component to connect successfully.
For more information on how to use connections with encryption properties, see Microsoft SQL JDBC documentation. |
|
Limitation |
Note that some features that are supported by other databases are not supported by Azure Synapse Analytics. For more information, see Unsupported table features. |