Feedback
Did this article resolve your question/issue?

   

Article

Does the Connect for ODBC/JDBC SQL Server drivers support the SQL Server 2016 "Always Encrypted" feature?

Information

 
TitleDoes the Connect for ODBC/JDBC SQL Server drivers support the SQL Server 2016 "Always Encrypted" feature?
URL NameDoes-the-connect-for-odbc-and-jdbc-sql-server-drivers-support-the-sql-server-2016-always-encrypted-feature
Article Number000179760
EnvironmentProduct: Progress DataDirect for ODBC/JDBC SQL Server driver
Version: JDBC 6.0 and ODBC 8.0
OS: All supported platforms
Database: SQL Server
Application: N/A
Question/Problem Description
SQL Server 2016 offers a feature known as the "Always Encrypted" configuration.  Do the SQL Server drivers support this feature?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
The Connect for JDBC SQL Server driver now supports "Always Encrypted" starting at patch level 6.0.0.0198
Refer to  Connect for JDBC hot fix download and install instructions for instructions on how to download and install the hot fix.

SQL Server "Always Encrypted" is also supported with the Connect for ODBC SQL Server 8.0 Wire Protocol driver (GA release). 

 
Workaround
Notes
Last Modified Date11/20/2020 6:56 AM
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.