Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now

Qlik Talend Products: Unable to Connect to Azure SQL Database after enabling TLS v1.2

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
KiranKumari_Biradar

Qlik Talend Products: Unable to Connect to Azure SQL Database after enabling TLS v1.2

Last Update:

Aug 29, 2025 3:00:09 AM

Updated By:

Xiaodi_Shi

Created date:

Aug 29, 2025 3:01:52 AM

You may encounter this issue that unable to connect to Azure SQL Database after enabling TLS v1.2 on the database side, and gives an error when executing the task on the Talend management Console side.

java.sql.SQLException: Reason: Login failed due to client TLS version being less than minimal TLS version allowed by the server.

 

jTDSwithTLSv1.2 .png

 

Resolution

When using the MSSQL components in Talend Studio, Qlik Talend components support 2 kinds of driver (explicit choice to make). The open source one JTDS or the official Microsoft jdbc driver.

It is recommended to use the official MSSQL driver to ensure greater compatibility. The jTDS is not recommended but can still be supported and this driver in a “deprecated” status,  Keep this possibility to use this driver for users who want to use it and for whom it remains compatible with their databases.

 

There are two solutions for this issue as belows

Solution 1

The jTDS driver prior 1.2 does not support TLS v1.2. Please use the official JDBC driver from Microsoft (switch to the official MSSQL driver to ensure greater compatibility).

Solution 2

Add ssl=require to the end of the JDBC connection URL (ex: jdbc:jtds:sqlserver://my-example-instance.c656df8582985.database.windows.net:1433;ssl=require), or in "Additional JDBC parameters" field of  MSSQL components and then re-publish the job and run on Talend management Console.

AzureDBConnection.png

AzureDBAdditionalSettings.png

 

Cause

The open source  jTDS driver, specifically earlier versions like 1.2, does not natively support TLS 1.2. This can lead to connection failures when connecting to SQL Server instances that enforce TLS 1.2, such as Azure SQL Managed Instances or on-premises servers configured to require TLS 1.2 for security reason. 

 

Related Content

publish-jobs-to-Talend-Cloud

 

Environment

Labels (1)
Version history
Last update:
Friday
Updated by: