Feedback
Did this article resolve your question/issue?

   

Article

Does the SQL Server legacy driver support SSL?

Information

 
TitleDoes the SQL Server legacy driver support SSL?
URL NameDoes-the-SQL-Server-legacy-driver-support-SSL
Article Number000111217
EnvironmentProduct: Connect for ODBC SQL Server driver
Version: 7.1
OS: All support platforms
Database: SQL Server
Application: All supported applications
Question/Problem Description
Does the Connect for ODBC SQL Server Legacy driver support SSL?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
The Connect for ODBC SQL Server legacy driver does not support SSL. For secure connections use the Connect for ODBC SQL Server Wire Protocol driver.

For additional information refer to the DataDirect documentation.

Note the SQL Server Legacy driver was retired in December 2018. There are no plans to continue the driver in version 8.0
 
Workaround
Notes
References to other documentation:
DataDirect Documentation, https://www.progress.com/documentation/datadirect-connectors
 
Last Modified Date4/8/2019 12:27 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.