An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release.

Refer to the following resources for additional information:

• Product Compatibility Guide: Provides the latest data source and platform support information. 
• Fixes: Describes the issues resolved since general availability.  
• Third-party Components Compatibility Matrix: Provides the latest information about the third-party components installed with the product.  

Version 8.0.2

Enhancements

• The driver is now compiled with Visual Studio 2022 compiler for Windows platforms. As a result, you must have Microsoft Visual C/C++ runtime version 14.40.33810 or higher on your machine to run the driver
• The driver has been enhanced to support Sybase Extended Password Encryption and Sybase Extended Plus Encrypted Password, which use an asymmetrical key type. This provides stronger password encryption for the secure transmission of public key passwords over networks.
• The driver has been enhanced to support binary and varbinary data types when using the bulk load protocol.
• A Password Encryption Tool, called ddencpwd, is now included with the product package. It encrypts passwords for secure handling in connection strings and odbc.ini files. At connection, the driver decrypts these passwords and passes them to the data source as required.
• The drivers using base version B0548 and later have been enhanced to include timestamp in the internal packet logs by default. If you want to disable the timestamp logging in packet logs, set PacketLoggingOptions=1. The internal packet logging is not enabled by default. To enable it, set EnablePacketLogging=1.
• The Driver Manager for UNIX/Linux has been enhanced to support setting the Unicode encoding type for applications on a per connection basis. By passing a value for the SQL_ATTR_APP_UNICODE_TYPE attribute using SQLSetConnectAttr, your application can specify the encoding at connection. This allows your application to pass both UTF-8 and UTF-16 encoded strings with a single environment handle.
  The valid values for the SQL_ATTR_APP_UNICODE_TYPE attribute are SQL_DD_CP_UTF8 and SQL_DD_CP_UTF16. The default value is SQL_DD_CP_UTF8.
• The driver supports the QUERY_TIMEOUT statement attribute on all UNIX/Linux platforms. This was formerly supported only on Windows.

Changed Behavior

• The driver has been updated to return Adaptive Server Enterprise as the DBMS name, instead of SQL Server, for the following:
  • SQLGetInfo calls
  • Error messages
• The TLSv1.1 and TLSv1.0 cryptographic protocols are now disabled by default and have been removed as selectable options for the Crypto Protocol Version (CryptoProtocolVersion) option on the Setup dialog. These protocols are no longer considered secure and, therefore, are no longer recommended for use. However, the driver still supports them for legacy servers that do not support more secure protocols.

Notes, Known Issues, and Limitations

• For values of the real data type, to comply with the SAP ASE server, the driver ensures the accuracy of the values loaded through bulk load only up to 6 digits.
• For values of the money data type, to comply with the SAP ASE server, if an application provides a scale (number of digits to the right of the decimal) greater than 4, the driver truncates it to 4.
• The driver does not support inserting data containing LOB columns using the bulk load protocol. In such cases, the driver throws a warning and falls back to the native protocol to continue executing the inserts.
• When using Bulk load to execute an insert statement, the operation will fail with an error message if non-identity columns are omitted from the statement.
• On the Logon dialog box, there is a Database drop-down list that displays the database names specified on the Connection tab of the ODBC SAP ASE Wire Protocol Driver Setup dialog box. This functionality is available in all cases except when connecting through the Test Connect button on the Setup dialog box. When connecting through the Test Connect button, only the default database specified on the General tab of the Setup dialog box is available.
• The driver does not support specifying values for the same connection option multiple times in a connection string or DSN. If a value is specified using the same attribute multiple times or using both long and short attributes, the connection may fail or the driver may not behave as intended.
• You may receive a 126 error when adding or configuring a data source stored on a network location. This is caused by the settings of the User Account Control (UAC) security feature on Windows 10. To work around this issue:
  1. From the Start menu, type regedit in the search field; then, select regedit from the results list. The Registry Editor window opens.
  2. Navigate to the following registry subkey:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  3. Right-click on the subkey; then, select New > DWORD Value.
  4. Rename the new value EnableLinkedConnections.
  5. Right-click EnableLinkedConnections, and then click Modify. The Edit DWORD Value window opens.
  6. In the Value data field, type 1. Click OK.
  7. Close the Registry Editor; then, restart your computer.
  Important: Implementing this fix disables security safeguards that are designed to protect your machine. Before starting, refer to the following Microsoft documentation for potential risks associated with disabling the UAC feature: http://windows.microsoft.com/en-us/windows/what-are-user-account-control-settings
• If you have installed an evaluation copy of the drivers and want to upgrade to a licensed version, you must use the Modify option of the installation program.
• When you first install a driver, you are given the option to install a default data source for that driver. We recommend that you install default data sources when you first install the drivers. If you do not install the default data source at this time, you will be unable to install a default data source for this driver later. To install a default data source for a driver after the initial installation, you must uninstall the driver and then reinstall it.
• All of the Release 8.0 Core Components (header files, etc.) needed for development of ODBC applications on UNIX and Linux are installed into the /include directory created by the product installer.
  Please read the notices.txt file in the installation directory for licensing information regarding the ODBC Core Components. Contact your Progress DataDirect representative if you have any questions.
  Developers using programming languages other than C++: The DataDirect ODBC Driver Manager is a C++ shared library. The ODBC Driver Manager can be used with any language that supports loading a C++ shared library; however, if you are using a programming language other than C++, you must take additional steps to ensure that the C++ libraries are initialized properly when loaded. If you are not using C++, consult your compiler documentation for instructions on using C++ shared libraries with your application.
• The DataDirect ODBC Driver Manager is a C++ shared library. The ODBC Driver Manager can be used with any language that supports loading a C++ shared library; however, if you are using a programming language other than C++, you must take additional steps to ensure that the C++ libraries are initialized properly when loaded. If you are not using C++, consult your compiler documentation for instructions on using C++ shared libraries with your application.
• A default installation of the product on UNIX and Linux assumes that the value of the LANG environment setting is en_US. If your locale is not set to en_US, the drivers may not return error messages properly. In this case, you must create a symbolic link in the <Install_Dir>/locale directory that has the same value as the LANG environment setting. This link must point to the <Install_Dir>/locale/en_US directory.
• The column attributes 1001 and 1002, which were assigned as DataDirect-specific attributes, were inadvertently used as system attributes by the Microsoft 3.0 ODBC implementation. Applications using those attributes must now use 1901 and 1902, respectively.
• Because of inconsistencies in the ODBC specification, users attempting to use SQL_C_NUMERIC parameters must set the precision and scale values of the corresponding structure and the descriptor fields in the Application Parameter Descriptor.
• Some IBM AIX C compilers, such as xlc 3.1.4, do not support the use of C++ build binaries. C developers on AIX should consult their compiler documentation and verify that their AIX C compiler supports the use of C++ shared libraries or the application could be unstable.
  Unexpected behavior may occur randomly if the LIBPATH variable exceeds 178 characters.

Version 7.1.6

Enhancements

• For AIX platforms, the ICU library files that are installed with the product have been upgraded to version 74.1. As a part of this upgrade, the ICU library file names have changed. For the 32-bit driver, the ICU file name has changed from libivicu28.a to libivicu.a. For the 64-bit driver, the ICU file name has changed from libddicu28.a to libddicu.a. Notes:
  • This upgrade does not apply to the other UNIX platforms.
  • This upgrade is available starting in build 08.02.1072 of the ICU library files.
  • libivicu27.a (32-bit) and libddicu27.a (64-bit) will continue to be included in the product package to support driver functionality.*
• For Windows platforms, the ICU library files that are installed with the product have been upgraded to version 74.1. As a part of this upgrade, the ICU library file names have changed. For the 32-bit driver, the ICU file name has changed from ivicu28.dll to ivicu.dll. For the 64-bit driver, the file name has changed from ddicu28.dll to ddicu.dll. Notes:
  • This upgrade is available starting in build 08.02.1072 of the ICU library files.
  • ivicu27.dll and ddicu27.dll will continue to be included in the product package to support driver functionality.*
• The Driver Manager has been upgraded to version 8.0. The purpose of this upgrade is to have all DataDirect for ODBC drivers use the latest version of the Driver Manager, which allows for faster security updates and a consistent user experience. Note that the Driver Manager is backward compatible. As part of this upgrade:
  • The following ICU library files have been added to the product package:
    • For UNIX: libivicu28.so (32-bit) and libddicu28.so (64-bit)
    • For Linux: libivicu.so (32-bit) and libddicu.so (64-bit)
  • The trace library file names have been changed for both UNIX and Linux:
    • 32-bit: From ivtrc27.so to ivtrc28.so
    • 64-bit: From ddtrc27.so to ddtrc28.so
  Note 1: libivicu27.so (32-bit) and libddicu27.so (64-bit) will continue to be included in the product package to support driver functionality.
  Note 2: The Driver Manager build included with the product is 08.02.1997 (U1987).
• For Linux platforms only, the ICU library files that are installed with the product have been upgraded to version 74.1. In addition, the ICU library file names have changed for Linux platforms:
  • For the 32-bit driver: From libivicu27.so to libivicu.so
  • For the 64-bit driver: From libddicu27.so to libddicu.so
  This upgrade is available starting in build 08.02.0965 of the ICU library files.
• For Windows platforms, the trace library file names have been changed from ivtrc27.dll to ivtrc28.dll (32-bit) and from ddtrc27.dll to ddtrc28.dll (64-bit) to have the same file names across all platforms. This change allows for faster release of security updates and a more consistent user experience.
  Note: To support the trace library file name change, the following ICU library files have been added to the product package: ivicu28.dll (32-bit) and ddicu28.dll (64-bit).
• The default version of the OpenSSL library has been upgraded to version 3.0.9, which fixes the security vulnerabilities listed on the following page: https://www.openssl.org/news/vulnerabilities-3.0.html.*

  Notes:

  • The driver supports the following OpenSSL 3.0 providers: Default and FIPS.
  • The FIPS provider is supported only on the following platforms: Windows 64-bit, Linux 64-bit, and AIX 64-bit.
  • When installing a new version of the product, the installer program will automatically replace the OpenSSL 1.1.1 library files with the OpenSSL 3.0 library files in the install directory, which will impact all the DataDirect ODBC drivers installed on a machine. Therefore, if you are using multiple 7.1 drivers, upgrade all your drivers to the latest version.
• The new CryptoLibName and SSLLibName connection options allow you to designate the OpenSSL libraries used when SSL is enabled.

Changed Behavior

• The installer program now requires you to install a JRE that is Java SE 11 or higher before running the installer. In earlier versions, the JRE used by the installer program was included in the product. However, to avoid potential security vulnerabilities, the installer program no longer includes a JRE. Instead, the installer program uses the JRE in your environment to allow for the most secure version of a JRE to be used.

  Notes:

  • This change does not affect the JVM requirements for the driver. For the latest driver requirements, refer to the Product Compatibility Guide.
  • The installer program cannot remove the already installed JRE files from the install directory automatically. Remove them manually.
• The product package no longer includes the ODBC Cursor library file (odbccurs.so) because it has some known security vulnerabilities that could potentially expose you to security risks.*
  Note: The installer program cannot remove the ODBC Cursor library file automatically while installing a new version of the driver. Remove it manually.
• The product no longer includes version 1.1.1 of the OpenSSL library. The library will reach the end of its product life cycle in September 2023 and will not receive any security updates after that. Note that continuing to use the library after September 2023 can potentially expose you to security vulnerabilities.*

  Note: As a result of this change, when installing a new version of the product, the installer program will automatically remove version 1.1.1 of the library from the install directory, which will impact all the DataDirect ODBC drivers installed on a machine.

• The product no longer includes version 1.0.2 of the OpenSSL library. The library has reached the end of its product life cycle and is not receiving security updates anymore. Note that continuing to use the library could potentially expose you to security vulnerabilities.*
  Note: As a result of this change, when installing a new version of the driver, the installer program will automatically remove version 1.0.2 of the library from the install directory.
• The Allowed OpenSSL Versions (AllowedOpenSSLVersions) connection option has been deprecated as the driver currently supports only version 3.0 of the OpenSSL library.
• The crypto protocol versions prior to TLSv1 are no longer supported.

Version 7.1.5

Enhancements

• The OpenSSL library was upgraded to version 1.0.0r, which fixes the CVE‐2015‐0204 (FREAK) vulnerability. See "RSA silently downgrades to EXPORT_RSA [Client] (CVE‐2015‐0204)" at https://www.openssl.org/news/secadv_20150108.txt for more
  information.
• The new PRNGSeedSource connection option allows you to specifies whether the driver uses a file or the RAND_poll function as the seed source for SSL key generation.
• The new PRNGSeedFile connection option allows you to specify the entropy‐source file or device used as a seed for SSL key generation.
• The new Crypto Protocol Version connection option allows you to specify the cryptographic protocols used when SSL is enabled. This option can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.

Version 7.1.4

Enhancements

• The new KeepAlive connection option allows you to use TCP Keep Alive to maintain idle TCP connections.

Version 7.1.3

No features introduced 

Version 7.1.2

No features introduced 

Version 7.1.1

No features introduced 

Version 7.1.0

No features introduced