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.  

ENHANCEMENTS

• The ICU library files that are installed with the Windows version of the product have been upgraded to version 74.1. In addition, 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 ICU file name has changed from ddicu28.dll to ddicu.dll. This upgrade is available starting in build 08.02.1072 of the ICU library files.*
  
• The ICU library files that are installed with the Linux version of the product have been upgraded to version 74.1. In addition, the ICU library file names have changed. For the 32-bit driver, the ICU file name has changed from libivicu28.so to  libivicu.so. For the 64-bit driver, the ICU file name has changed from libddicu28.so to libddicu.so. This upgrade is available starting in build 08.02.0965 of the ICU library files.*
• The installer program has been enhanced to support Azul Zulu JRE 11. As a result of this change, the installer has ended support for platforms that do not support Java SE 8 or higher. The installer supports the following operating systems after the enhancement:
  • Windows 8.1 or higher
  • Windows Server 2012 RC2 or higher
  • UNIX/Linux: Any operating system on a machine using a JRE that is Java SE 8 or higher (LTS version), including Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
  Important: These changes do not affect the operating system requirements of the driver.*
• The driver supports the fetching of multiple requests simultaneously with the Read Ahead (ReadAhead) connection option. This option improves throughput and performance. Refer to Read Ahead for details.*
• 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. See Password Encryption Tool (UNIX/Linux only) for details.*

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.
  • To install the 32-bit drivers on 64-bit Windows platforms and start the SQL engine service, the installer requires the 32-bit version of Java SE 11 or higher installed on your machine and defined on your path.
• 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 installer program has been updated to no longer install common components for drivers that do not use them. As a result, the installer program no longer installs the following common components for the TeamCity driver:*
  • OpenSSL library files, such as ivopenssl30.so, ddopenssl30.so, fips.so, and openssl.cnf.
  • Curl library files, such as libivcurl28.so and libddcurl28.so.

  If the files are not used by any other DataDirect driver on your machine, you can safely remove them from existing product directories.

• On Windows platforms, the default setting for the SQL Engine Mode (SQLEngineMode) option has changed to 1 (Server). Refer to SQL Engine Mode for details.*
• The Server Name (ServerName) connection option has been renamed Host Name (HostName). To support existing configurations, the ServerName attribute will continue to be supported as an alias for the Host Name option. See Host Name for details. 

Version 8.0.0

Features

• The driver supports SQL read-only access to TeamCity Enterprise and Community editions. Refer to Supported SQL statements and extensions for details. 
• The driver supports all ODBC Core and Level 1 functions and some Level 1 and Level 2 features. Refer to ODBC API and scalar functions in the Progress DataDirect for ODBC Drivers Reference for additional information. 
• The driver supports TeamCity data types through data type inference. Refer to Data types for details. 
• The driver supports Basic authentication. Refer to Basic authentication for details. 
  
• The driver supports Bearer token authentication. Refer to Bearer token authentication for details. 
• The driver supports the handling of large result sets with paging and the Fetch Size (FetchSize) connection option. Refer to Fetch Size for details. 
  
• On Windows platforms, the driver includes a redesigned ODBC setup dialog, the DataDirect ODBC Driver Configuration Manager, for quick configuration and testing of your driver. This Configuration Manager allows you to:
  • Configure data sources
  • Generate and edit connection strings
  • Test connect data sources and connection strings
  • Execute SQL commands for testing
    
  • Access connection property descriptions and the full product documentation
  Refer to Configuring data sources with the Configuration Manager and Generating connection strings with the Configuration Manager for details.