Progress DataDirect for ODBC for Google Analytics 4
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:
Version 8.0.0
Changed Behavior
Features
- The driver supports SQL read-only access to Google Analytics using Google Analytics 4 (GA4) Data and Admin API. 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 for details.
- The driver supports Google Analytics data types. Refer to Data types for details.
- The driver supports OAuth 2.0 authentication. Refer to OAuth 2.0 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 an enhanced setup dialog, the DataDirect ODBC Driver Configuration Manager, for quick configuration and testing of your driver. This Configuration Manager allows you to:
- Add tables to the relational view of Google Analytics data
- Configure data sources
- Generate and edit connection strings
- Test connect data sources and connection strings
- Execute SQL commands for testing;
- Access connection option 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.
- 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.*
Progress DataDirect Connect for ODBC Text Driver
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:
Version 7.1.6
Enhancements
- Some components of the driver are now compiled with a 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.*
- 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). - 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.*
- The drivers using base version B0649 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 Connect64 (64-bit) version of the Text driver is now generally available. This new driver provides 64-bit support for the features and functionality offered by the earlier DataDirect Connect (32-bit) version of the driver. In addition, for the
Connect64 driver, support for HP-UX IPF has been added.*
Notes:
- The Connect64 Text driver uses a driver-specific installer, instead of the Connect Series installer. Both installers are available on the Progress website.
- The control numbers available in the new control number format (8.0 control numbers) must be used for installing the Connect64 Text driver, instead of those available in the old format (7.1 control numbers).
- 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.
This enhancement is available in build 07.16.0398 of the driver manager.
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.
Version 7.1.5
No features introduced
Version 7.1.4
No features introduced
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
Progress DataDirect for ODBC for SAP ASE Wire Protocol Driver
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:
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.
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
Progress DataDirect for ODBC for Oracle Service Cloud
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:
Version 7.1.6
Enhancements
- Some components of the driver are now compiled with a 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.*
- 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). - 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.*
- The drivers using base version B0649 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.
This enhancement is available in build 07.16.0398 of the driver manager.
- The new NamedIDBehavior config option allows you to determine whether the Name attribute of NamedID fields is exposed in the relational map. This option can be used to avoid "poor performing query" errors by reducing the size of result sets. Refer to "Poor performing query" error message and NamedIDBehavior (Config Option) for details.*
- The new Min Long Varchar Size connection option allows you to fetch SQL_LONGVARCHAR columns whose size is smaller than the minimum imposed by some third-party applications. Refer to Min Long Varchar Size for details.
- The new Varchar Threshold connection option allows you to fetch columns that would otherwise exceed the upper limit of the SQL_VARCHAR type for some third-party applications. Refer to Varchar Threshold 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.
Version 7.1.5
Features
- The driver supports Oracle RightNow CX API
- Supports all ODBC Core functions.
- Supports the core SQL-92 grammar.
- Supports client-side data caching.
Progress DataDirect Connect and Connect64 for ODBC SQL Server Wire Protocol Driver
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:
Version 8.0.2
Enhancements
- The driver has been enhanced to support PKCS #12 files as keystore providers
for the Always Encrypted feature. PKCS #12 files can be stored locally on
the disk on any platform the driver supports. You can configure the driver
to use a PKCS #12 file using the new AE Keystore Location (AEKeyStoreLocation)
and AE Keystore Secret (AEKeyStoreSecret) connection options. Refer to
Using keystore providers for details.
- The driver is now compiled with a Visual Studio 2022 compiler for the 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.
- 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. 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.*
- 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 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 driver has been enhanced to support Microsoft Entra ID authentication using
managed identities for Azure resources. You can configure this feature using
the updated Authentication Method (AuthenticationMethod) and User Name
(LogonID) options. See Microsoft Entra ID authentication for details.*
Available: 7/4/2024 | 08.02.1756 - The driver has been enhanced to support Microsoft Entra ID authentication using
service principal users. You can configure this feature using the updated
Authentication Method (AuthenticationMethod), User Name (LogonID) and Password
(Password) options. See Microsoft Entra ID authentication for details.*
Available: 7/4/2024 | 08.02.1756 - The driver has been enhanced to support the TLSv1.3 cryptographic protocol using SQL Server 2022. To enable TLSv1.3 encryption, set the Encryption Method (EncryptionMethod) option to the new value
8 (Strict). See Encryption Method for details.*
Available: 3/18/2024 | 08.02.1617
- For Linux platforms, 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 on Linux, the ICU file name has changed from libivicu28.so to libivicu.so. For the 64-bit driver on Linux, the ICU file name has changed from libddicu28.so to libddicu.so. This upgrade does not apply to UNIX platforms.
This upgrade is available starting in build 08.02.0965 of the ICU library files.*
Available: 3/18/2024 | 08.02.1617 - Note: OpenSSL library 3.0.9 has been replaced with a later version. For the latest information about the third-party components that are installed with the product, refer to the Third-party Components Compatibility Matrix.
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 8.0 drivers, upgrade all your drivers to the latest version.
- If you are using both 8.0 and 7.1 versions of the driver, copy the xxtls27.dll/libxxtls27.so[.sl] file to a different location before installing a new version of the 8.0 driver. Copy it back to the install directory once the installation
is complete.
Refer to TLS/SSL server authentication and TLS/SSL server authentication for details.
- The driver has been enhanced to support the Windows certificate store for TLS/SSL server authentication. Refer to TLS/SSL server authentication for details.*
- The driver has been enhanced to support TLS/SSL server authentication for the applications deployed in a serverless environment. The driver stores the TLS/SSL certificates in memory and lets applications use TLS/SSL server authentication without storing
the truststore file on the disk. To use this enhancement, specify the content of the certificate in the refreshed Trust Store (Truststore) connection option or the new SQL_COPT_INMEMORY_TRUSTSTORECERT pre-connection attribute. Refer to the Trust Store and Using SQL_COPT_INMEMORY_TRUSTSTORECERT for details.*
- On Windows, the driver has been enhanced to support connecting to servers using aliases created by the SQL Server Configuration Manager. To support this feature, the Host Name (HostName) connection option has been refreshed to accept alias names as
valid values. The driver uses the server name and port number provided by the alias when establishing a connection. Refer to Host Name for details.*
- The driver has been updated to return the server name to which you are connected for the value of SQL_SERVER_NAME when executing SQLGetInfo. In earlier versions of the driver, the value returned for SQL_SERVER_NAME would be the setting of the Host
Name (HostName) connection option. The driver will now return the server name string that it receives from the server when connecting to the database as the value for SQLGetInfo(SQL_SERVER_NAME).*
- The driver has been enhanced with the new Keep Connection Active (KeepConnectionActive) and Socket Idle Time (SocketIdleTimeCheckInterval) connection options. Together, these options provide you with a method to keep active idle connections to Azure
SQL Database, Azure Synapse Analytics through Azure SQL Gateway, or to databases that enforce timeouts for inactivity. Refer to Keep Connection Active and Socket Idle Time for details.*
- The driver has been enhanced to support inserts into SQL Server IDENTITY columns in replication scenarios. Either the Enable Replication User (EnableReplicationUser) connection option or the SQL_COPT_REPLICATION_USER connection attribute (numeric
value 1080) can be used to allow inserts into IDENTITY columns. When the replication user feature is set to 1 (Enabled), explicit values can be inserted into IDENTITY columns defined as NOT FOR REPLICATION. If different values are specified for
the Enable Replication User option and the SQL_COPT_REPLICATION_USER attribute, driver behavior is determined by the value of the SQL_COPT_REPLICATION_USER attribute. Refer to Inserts on IDENTITY columns in data replication scenarios and Enable Replication User for details.*
- The driver has been enhanced to support access token authentication programmatically with the use of a pre-connection attribute SQL_COPT_SS_ACCESS_TOKEN. Refer to Access token authentication for more information.*
- The driver has been enhanced to support distributed transactions. It implements the XA interface to enable support for distributed transactions. Refer to XA interface support for details.
- The driver has been enhanced to use sp_describe_undeclared_parameters, a SQL Server system stored procedure, to fetch parameter metadata. With this enhancement, the driver can return more accurate parameter metadata for both simple and complex queries. However, it cannot determine if a parameter allows NULL values; hence, it returns SQL_NULLABLE_UNKNOWN for the nullable fields. Note that the driver does not call sp_describe_undeclared_parameters
to fetch parameter metadata when Always Encrypted functionality is enabled
(ColumnEncryption=Enabled).* - The drivers using base version B0649 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 has been enhanced to support the Always Encrypted feature. Beginning with SQL Server 2016, Azure SQL and SQL Server databases support Always Encrypted, which allows sensitive data to be stored on the server in an encrypted state such that
the data can only be decrypted by an authorized application. The following are highlights of this enhancement:
- The driver detects all supported native data types in encrypted columns and transparently encrypts values bound to SQL parameters or decrypts values returned in results and output parameters.
- The driver supports configurable caching of column encryption keys for improved performance.
- The driver supports using Windows Certificate Store and Azure Key Vault as keystore providers.
You can enable support for Always Encrypted using the new Column Encryption, Key Store Principal, Key Store Secret, and Key Cache Time To Live connection options. Refer to Always Encrypted for details.
- The new AllowedOpenSSLVersions option determines which version of the OpenSSL library file the driver uses for data encryption when multiple versions are installed with the product. For example, when specifying a value of 1.1.1 (AllowedOpenSSLVersions=1.1.1) the driver uses the 1.1.1 version of the library that is installed with the driver.*
- The driver has been enhanced to transparently connect to Microsoft Azure Synapse Analytics and Microsoft Analytics Platform System data sources. Refer to Support for Azure Synapse Analytics and Analytics Platform System for details.
- The driver has been enhanced to support connecting to a proxy server through an HTTP connection. HTTP proxy support is configurable with the new Proxy Host, Proxy Mode, Proxy Password, Proxy Port, and Proxy User connection options. Refer to Connection option descriptions for details.
- The new Enable Server Side Cursors connection option allows you to determine which server-side cursors are enabled for the data source. Refer to Enable Server Side Cursors for details.
- The driver is enhanced to support Azure Active Directory (Azure AD) authentication. Azure AD authentication is an alternative to SQL Server Authentication for Azure SQL Database that allows you to centrally manage identities of database users. Refer to Azure Active Directory Authentication for details.
- The driver has been enhanced to support Always On Availability Groups.
Introduced in SQL Server 2012, Always On Availability Groups is a replica-database environment that provides a high-level of data availability, protection, and recovery. To support this enhancement, the following updates
have been made to the driver:
- The Host Name option has been updated to support the virtual network name (VNN) of the availability group listener as a valid value. To connect to an Always On Availability group, you must specify the VNN using this option.
- The new Application Intent option allows you to control whether the driver requests read-only routing, thereby improving efficiency by reducing the workload on read-write nodes. For details, refer to the readme installed with the product.
- The new MultiSubnetFailover option allows the driver to attempt parallel connections to all the IP addresses associated with an availability group when the primary listener is unavailable. This offers improved response time over traditional
failover, which attempts connections to alternate servers one at a time. For details, refer to the readme installed with the product.
Refer to Multi-Subnet Failover, Host Name, and Application Intent for details.
- The driver and Driver Manager have been enhanced to support UTF-8 encoding in the odbc.ini and odbcinst.ini files. Refer to Character encoding in the odbc.ini and odbcinst.ini files in the Progress DataDirect for ODBC Drivers Reference 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.
- 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.
Version 7.1.6
Enhancements
- The driver has been updated with OpenSSL library version 1.0.2k.*
Note: OpenSSL library 1.0.2k has been replaced with version 1.0.2n. - The default OpenSSL library version has been updated to 1.0.2j.*
Note: OpenSSL library 1.0.2j has been replaced with version 1.0.2n. - The default OpenSSL library version has been updated to 1.0.2h.*
Note: OpenSSL library 1.0.2h has been replaced with version 1.0.2n. - The default OpenSSL library version has been updated to 1.0.2g.*
Note: OpenSSL library 1.0.2g has been replaced with version 1.0.2n. - The default OpenSSL library version has been updated to 1.0.2f.
Note: OpenSSL library 1.0.2f has been replaced with version 1.0.2n. - The new CryptoLibName and SSLLibName connection options allow you to designate the OpenSSL libraries used when SSL is enabled.
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 driver has been enhanced to support NTLMv2 authentication, which can be
enabled using the AuthenticationMethod connection option. - 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
Progress DataDirect for ODBC for Greenplum Wire Protocol Driver
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:
Version 8.0.2
Enhancements
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 TLSv1.1 and TLSv1.0 cryptographic protocols are now disabled by default and have been removed as selectable values 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 TLSv1.1 and TLSv1.0 for legacy servers that do not support more secure protocols.
- The HP-UX PA-RISC platform is no longer supported.
- The default value for the Batch Mechanism (BatchMechanism) connection option has been changed to 3 (Copy).
- The default values for the Unbounded Numeric Precision (UnboundedNumericPrecision) and Unbounded Numeric Scale (UnboundedNumericScale) options have been changed to -1.
Version 7.1.6
Enhancements
- 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 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 driver has been enhanced with the new Batch Mechanism (BatchMechanism) connection option, which specifies the preferred mechanism for executing batch insert operations. By setting Batch Mechanism to 2 (MultiRowInsert) or 3 (Copy), the driver can
achieve substantial performance gains when performing batch inserts. The default setting is BatchMechanism=1 (SingleRowInsert). Refer to Batch Mechanism for details.
- OpenSSL library 1.1.1l has been replaced with version 3.0.9. In addition to fixing multiple new vulnerabilities, version 3.0.9 also addresses the vulnerabilities resolved by version 1.1.1l:*
- SM2 Decryption Buffer Overflow (CVE-2021-3711)
- Read buffer overruns processing ASN.1 strings (CVE-2021-3712)
Version 1.1.1l also addresses vulnerabilities resolved by earlier versions of the library. For more information on the installed library files, refer to the readme.
For more information on the OpenSSL vulnerabilities resolved by this upgrade,
refer to the corresponding OpenSSL announcements at
https://www.openssl.org/news/vulnerabilities-1.1.1.html.
- OpenSSL library 1.1.1k has been replaced with version 1.1.1l. In addition to fixing multiple new vulnerabilities, version 1.1.1l also addresses the vulnerabilities resolved by version 1.1.1k:*
- CA certificate check bypass with X509_V_FLAG_X509_STRICT (CVE-2021-3450)
- NULL pointer deref in signature_algorithms processing (CVE-2021-3449)
- Null pointer deref in X509_issuer_and_serial_hash() (CVE-2021-23841)
- Integer overflow in CipherUpdate (CVE-2021-23840)
- OpenSSL library 1.1.1i has been replaced with version 1.1.1l. In addition to fixing multiple new vulnerabilities, version 1.1.1l also addresses the vulnerability resolved by version 1.1.1i: Incorrect behavior of the GENERAL_NAME_cmp function (CVE-2020-1971).*
- OpenSSL library 1.1.1g has been replaced with version 1.1.1l. In addition to fixing multiple new vulnerabilities, version 1.1.1l also addresses the vulnerabilities resolved by version 1.1.1g:*
- Segmentation fault in SSL_check_chain (CVE-2020-1967)
- rsaz_512_sqr overflow bug on x86_64 (CVE-2019-1551)
- The drivers using base version B0649 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.*
- OpenSSL library 1.0.2r has been replaced with version 1.0.2u. In addition to fixing multiple new vulnerabilities, version 1.0.2u also addresses the vulnerabilities resolved by version 1.0.2r.*
Version 1.0.2u of the OpenSSL library fixes the following
security vulnerabilities:
- x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli (CVE-2019-1563)
- Padding Oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey (CVE-2019-1563)
- Compute ECC cofactors if not provided during EC_GROUP construction (CVE-2019-1547)
- Installation paths in diverse Windows builds (CVE-2019-1552)
Note: By default, the driver will attempt to load version 1.1.1 of the library; however, if the library cannot be loaded, the driver will fall back to version 1.0.2.
- The default OpenSSL library version has been updated to 1.1.1d.*
- The default OpenSSL library version has been updated to 1.0.2r.*
- The default OpenSSL library version has been updated to 1.0.2n.*
- The default OpenSSL library version has been updated to 1.0.2k.*
- The default OpenSSL library version has been updated to 1.0.2j.* .
- The default OpenSSL library version has been updated to 1.0.2h.*
- The default OpenSSL library version has been updated to 1.0.2g.*
- The default OpenSSL library version has been updated to 1.0.2f.
- The new CryptoLibName and SSLLibName connection options allow you to designate the OpenSSL libraries used when SSL is enabled. Refer to CryptoLibName and SSLLibName for details.
- The driver has been enhanced to support Kerberos Authentication. Refer to Kerberos Authentication for details.
Changed Behavior
- 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.
- The AuthenticationMethod connection option has been refreshed with a new valid value for enabling Kerberos Authentication. To use Kerberos authentication with the driver, set AuthenticationMethod=4. Refer to Authentication Method for details.
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 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. - The new Unbounded Numeric Precision connection option allows you to
define the precision for unbounded NUMERIC columns when described
within the column, parameter, result set, or table metadata. - The new Unbounded Numeric Scale connection option allows you to
define the scale for unbounded NUMERIC columns described within
the column, parameter, result set, or table metadata.
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
Enhancements
- Support for SSL data encryption.
Version 7.1.2
No features introduced
Version 7.1.1
No features introduced
Version 7.1.0
No features introduced
Progress DataDirect Connect XE and Connect64 XE for ODBC for Impala Wire Protocol Driver
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:
Version 7.1.6
Enhancements
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.
- The AuthenticationMethod connection option has been refreshed with a new valid value for enabling Kerberos Authentication. To use Kerberos authentication with the driver, set AuthenticationMethod=4. Refer to Authentication Method for details.
Version 7.1.5
No features introduced
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
Supported with the following Apache Hive versions:
- Cloudera Impala database server and formally certified with the following File formats and storage handlers:
- File Formats: Parquet, Text File
- Storage Handlers: HBase
Features
- Returns result set metadata for parameterized statements
that have been prepared but not yet executed. - Supports parameter arrays, processing the arrays as a series of
executions, one execution for each row in the array. - Provides a connection option that allows you to configure
the driver to report that it supports transactions, although
Hive does not support transactions. This provides a workaround
for applications that do not operate with a driver
that reports
transactions are not supported.
- Provides a connection option that allows you to set a default limit for
the number of rows returned when an ORDER BY clause is submitted. This
provides a workaround for applications that are not compatible with
Impala's requirement
that ORDER BY clauses limit the number of rows returned. - The driver provides support for the following standard SQL
functionality:
- Create Index, Create Table, and Create View
- Insert, Update, and Delete
- Drop Index and Drop Table
Progress DataDirect Connect for ODBC Btrieve Driver
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:
Version 7.1.6
Enhancements
- Some components of the driver are now compiled with a 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 ICU library file that is installed with the product has been
upgraded to version 74.1. As a part of this upgrade, the ICU library
file name has changed from ivicu28.dll to ivicu.dll. Notes:
- This upgrade is available starting in build 08.02.1072 of the ICU
library file.
- The ivicu27.dll file will continue to be included in the product package to
support driver functionality.
- The trace library file name has been changed from ivtrc27.dll to
ivtrc28.dll to have the same file name across all DataDirect for
ODBC drivers. 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 file has been added to the product package: ivicu28.dll. - 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.
Version 7.1.5
No features introduced
Version 7.1.4
No features introduced
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
Progress DataDirect for ODBC for Amazon Redshift Wire Protocol Driver
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:
Version 8.0.0
Enhancements
- The driver is now compiled with a Visual Studio 2022 compiler for the 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.
- 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 AIX platforms. 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. 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.*
- 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 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.*
- For Linux platforms, 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 on Linux, the ICU file name has changed from libivicu28.so to libivicu.so. For the 64-bit driver on Linux, the ICU file name has changed from libddicu28.so to libddicu.so. This upgrade does not apply to UNIX platforms.
This upgrade is available starting in build 08.02.0965 of the ICU library files.* - Note: OpenSSL library 3.0.9 has been replaced with a later version. For the latest information about the third-party components that are installed with the product, refer to the Third-party Components Compatibility Matrix.
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 8.0 drivers, upgrade all your drivers to the latest version.
- If you are using both 8.0 and 7.1 versions of the driver, copy the xxtls27.dll/libxxtls27.so[.sl] file to a different location before installing a new version of the 8.0 driver. Copy it back to the install directory once the installation
is complete.
- 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.*
- The driver has been enhanced to support Azure Active Directory (Azure AD) authentication. It allows administrators to centrally manage user permissions to Amazon Redshift. When Azure AD authentication is enabled, all communications to Amazon Redshift are encrypted. Refer to Azure Active Directory authentication for details.
- The driver has been enhanced to support the following data types: Float, Tinyint, Wchar, and Wvarchar.
- The drivers using base version B0649 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.
This enhancement is available in build 08.02.0449 of the driver manager.
- The new AllowedOpenSSLVersions option determines which version of the OpenSSL library file the driver uses for data encryption when multiple versions are installed with the product. For example, when specifying a value of 1.1.1 (AllowedOpenSSLVersions=1.1.1) the driver uses the 1.1.1 version of the library that is installed with the driver.*
- The driver is now compiled using Visual Studio 2015 for improved security.
- Support for connecting to a proxy server through an HTTP connection. HTTP proxy support is configurable with five new connection options: Proxy Host, Proxy Mode, Proxy password, Proxy Port, and Proxy User. Refer to Connection option descriptions for details.
- The driver has been enhanced to support the TimestampTZ data type. Refer to Data types and Fetch TSWTZ as Timestamp for details.
- The new Fetch TSWTZ as Timestamp option allows you to determine whether the driver returns column values of the TimestampTZ data type as the ODBC data type SQL_TYPE_TIMESTAMP or SQL_VARCHAR. Refer to Fetch TSWTZ as Timestamp for details.
- The driver has been enhanced to support the HOUR, MINUTE, MONTH, QUARTER, SECOND, WEEK, and YEAR ODBC functions for improved support of third-party applications such as Tableau.
- The driver includes a new Tableau data source file (Windows only) that provides improved functionality when accessing your data with Tableau. Refer to Accessing data in Tableau (Windows only) for details.
- The driver and Driver Manager have been enhanced to support UTF-8 encoding in the odbc.ini and odbcinst.ini files. Refer to Character encoding in the odbc.ini and odbcinst.ini files 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.
- 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 default value for Crypto Protocol Version has been updated to
TLSv1.2,TLSv1.1,TLSv1. This change improves the security of the driver by employing only the most secure cryptographic protocols as the default behavior. Refer to Crypto Protocol Version for details.
Version 7.1.6
Enhancements
- The driver has been updated with OpenSSL library version 1.0.2k.*
Note: OpenSSL library 1.0.2k has been replaced with version 1.0.2n.
Version 7.1.5
Enhancements
- The driver has been enhanced to optimize the performance of batch inserts.
- The OpenSSL library was upgraded to version 1.0.0r.
Note: OpenSSL library 1.0.0r has been replaced with version 1.0.2n. - The new CryptoProtocolVersion 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
Features
- The driver supports Amazon Web Services API.
- The driver supports all ODBC Core and Level 1 functions.
- The driver supports the core SQL 92 grammar.
- The driver supports DataDirect Connection Pooling.
- The driver supports advanced security features, including SSL data encryption.
- The driver supports configurable connection failover protection.
Progress DataDirect for ODBC for Sybase IQ Wire Protocol Driver
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:
Version 8.0.2
Enhancements
- The driver is now compiled with a Visual Studio 2022 compiler for the 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.
- 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. 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.*
- 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 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.*
- For Linux platforms, 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 on Linux, the ICU file name has changed from libivicu28.so to libivicu.so. For the 64-bit driver on Linux, the ICU file name has changed from libddicu28.so to libddicu.so. This upgrade does not apply to UNIX platforms. 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 has 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.
- 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.
- When calling the catalog functions in which the catalog name is passed as an argument, the driver now returns an empty result set instead of an error.
- 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 Sybase IQ Wire Protocol 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.
Version 7.1.6
No features introduced
Version 7.1.5
No features introduced
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
Progress DataDirect for ODBC for MySQL Wire Protocol Driver
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:
Version 8.0.2
Enhancements
- The driver is now compiled with a Visual Studio 2022 compiler for the 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.
- 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. 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.*
- 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 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.*
- For Linux platforms, 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 on Linux, the ICU file name has changed from libivicu28.so to libivicu.so. For the 64-bit driver on Linux, the ICU file name has changed from libddicu28.so to libddicu.so. This upgrade does not apply to UNIX platforms.
This upgrade is available starting in build 08.02.0965 of the ICU library files.* - Note: OpenSSL library 3.0.9 has been replaced with a later version. For the latest information about the third-party components that are installed with the product, refer to the Third-party Components Compatibility Matrix.
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 8.0 drivers, upgrade all your drivers to the latest version.
- If you are using both 8.0 and 7.1 versions of the driver, copy the xxtls27.dll/libxxtls27.so[.sl] file to a different location before installing a new version of the 8.0 driver. Copy it back to the install directory once the installation
is complete.
Refer to TLS/SSL server authentication and TLS/SSL client authentication for details.
- 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 has been enhanced to support the Windows certificate store for TLS/SSL server authentication. Refer to the TLS/SSL server authentication for details.*
- The driver has been enhanced to support TLS/SSL server authentication for the applications deployed in a serverless environment. The driver stores the TLS/SSL certificates in memory and lets applications use TLS/SSL server authentication without storing
the truststore file on the disk. To use this enhancement, specify the content of the certificate in the refreshed Trust Store (Truststore) connection option or the new SQL_COPT_INMEMORY_TRUSTSTORECERT pre-connection attribute. Refer to the Trust Store and Using SQL_COPT_INMEMORY_TRUSTSTORECERT for details.*
- The driver has been enhanced to support the JSON data type. Refer to Data types for more 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.*
- OpenSSL library 1.1.1l has been replaced with version 1.1.1n. In addition to fixing multiple new vulnerabilities, version 1.1.1n also addresses the vulnerabilities resolved by version 1.1.1l:*
- SM2 Decryption Buffer Overflow (CVE-2021-3711)
- Read buffer overruns processing ASN.1 strings (CVE-2021-3712)
- The driver has been enhanced to support connecting to a proxy server through an HTTP connection. HTTP proxy support is configurable with five new connection options: Proxy Mode (ProxyMode), Proxy Host (ProxyHost), Proxy Port (ProxyPort), Proxy Password
(ProxyPassword), and Proxy User (ProxyUser). Refer to Proxy server for details.
- For Windows platforms, a Power BI connector is now included with the product package.You can use this connector to access your MySQL data with Power BI. Refer to the Power BI (Windows only) for details.
- The Batch Mechanism (BatchMechanism) connection option has been added to the driver. When BatchMechanism is set to 2 (MultiRowInsert), the driver executes a single insert for all the rows contained in a parameter array. MultiRowInsert is the default
setting and provides substantial performance gains when performing batch inserts. Refer to Batch Mechanism for details.
- The driver has been enhanced to support the sha256_password and caching_sha2_password authentication plugins.
- For UNIX/Linux platforms, 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. Refer to the user's guide 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.
- 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.
Version 7.1.6
Enhancements
- The default version of the OpenSSL library has been upgraded to version 1.1.1k, which fixes the following security vulnerabilities:*
- CA certificate check bypass with X509_V_FLAG_X509_STRICT (CVE-2021-3450)
- NULL pointer deref in signature_algorithms processing (CVE-2021-3449)
- Null pointer deref in X509_issuer_and_serial_hash() (CVE-2021-23841)
- Integer overflow in CipherUpdate (CVE-2021-23840)
Version 1.1.1k also addresses vulnerabilities resolved by earlier versions of the library. For more information on the installed library files, refer to the readme.
For more information on the OpenSSL vulnerabilities resolved by this upgrade,
refer to the corresponding OpenSSL announcements at
https://www.openssl.org/news/vulnerabilities-1.1.1.html.
- OpenSSL library 1.1.1i has been replaced with version 1.1.1k. In addition to fixing multiple new vulnerabilities, version 1.1.1k also addresses the vulnerability resolved by version 1.1.1i: Incorrect behavior of the GENERAL_NAME_cmp function (CVE-2020-1971).*
- OpenSSL library 1.1.1g has been replaced with version 1.1.1k. In addtion to fixing multiple new vulnerabilities, version 1.1.1k also addresses vulnerabilities resolved by version 1.1.1g:*
- Segmentation fault in SSL_check_chain (CVE-2020-1967)
- rsaz_512_sqr overflow bug on x86_64 (CVE-2019-1551)
- The drivers using base version B0649 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.*
- OpenSSL library 1.0.2r has been replaced with version 1.0.2u. In addition to fixing multiple new vulnerabilities, version 1.0.2u also addresses the vulnerabilities resolved by version 1.0.2r.*
Version 1.0.2u of the OpenSSL library fixes the following
security vulnerabilities:
- x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli (CVE-2019-1563)
- Padding Oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey (CVE-2019-1563)
- Compute ECC cofactors if not provided during EC_GROUP construction (CVE-2019-1547)
- Installation paths in diverse Windows builds (CVE-2019-1552)
Note: By default, the driver will attempt to load version 1.1.1 of the library; however, if the library cannot be loaded, the driver will fall back to version 1.0.2.
- 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.
This enhancement is available in build 07.16.0398 of the driver manager.
- The default OpenSSL library version has been updated to 1.1.1d.*
- The new AllowedOpenSSLVersions option determines which version of the OpenSSL library file the driver uses for data encryption when multiple versions are installed with the product. For example, when specifying a value of 1.1.1 (AllowedOpenSSLVersions=1.1.1) the driver uses the 1.1.1 version of the library that is installed with the driver.*
- The default OpenSSL library version has been updated to 1.0.2r.*
- The default OpenSSL library version has been updated to 1.0.2n.*
- The default OpenSSL library version has been updated to 1.0.2k.*
- The default OpenSSL library version has been updated to 1.0.2j.*
- The default OpenSSL library version has been updated to 1.0.2h.*
- The default OpenSSL library version has been updated to 1.0.2g.*
- The default OpenSSL library version has been updated to 1.0.2f.
- The new CryptoLibName and SSLLibName connection options allow you to
designate the OpenSSL libraries used when SSL is enabled.
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 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
Progress DataDirect for ODBC for PostgreSQL Wire Protocol Driver
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:
Version 8.0.2
Enhancements
- The driver is now compiled with a Visual Studio 2022 compiler for the 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 is enhanced to support Microsoft Entra ID authentication using user
names and passwords. You can configure this feature using the updated
Authentication Method (AuthenticationMethod), User Name (LogonID), and Password
(Password) options, and the new Azure Tenant ID (AzureTenantID) option. Refer to Microsoft Entra ID authentication for more information.
Available: 8/26/2024 | 08.02.2829 - The driver has been enhanced to support Microsoft Entra ID authentication using
service principal users. You can configure this feature using the updated
Authentication Method (AuthenticationMethod), User Name (LogonID), and Password
(Password) options, and the new Azure Tenant ID (AzureTenantID) option. Refer to Microsoft Entra ID authentication for more information.
Available: 8/26/2024 | 08.02.2829 - 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. 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.*
- 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 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 driver has been enhanced to support the TLSv1.3 cryptographic protocol. As part of this enhancement, the default cryptographic protocols enabled by the driver have been updated to TLSv1.3 and TLSv1.2. Refer to Crypto Protocol Version for more information.
Available: 7/4/2024 | 08.02.2745 - For Linux platforms, 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 on Linux, the ICU file name has changed from libivicu28.so to libivicu.so. For the 64-bit driver on Linux, the ICU file name has changed from libddicu28.so to libddicu.so. This upgrade does not apply to UNIX platforms.
This upgrade is available starting in build 08.02.0965 of the ICU library files.* - The driver has been enhanced to support MERGE against PostgreSQL 15 and later. MERGE is a SQL command that modifies rows in the target table using the data from the source table. It can conditionally INSERT, UPDATE or DELETE rows in a single statement,
eliminating the need to write multiple procedural statements.
- Note: OpenSSL library 3.0.9 has been replaced with a later version. For the latest information about the third-party components that are installed with the product, refer to the Third-party Components Compatibility Matrix.
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 8.0 drivers, upgrade all your drivers to the latest version.
- If you are using both 8.0 and 7.1 versions of the driver, copy the xxtls27.dll/libxxtls27.so[.sl] file to a different location before installing a new version of the 8.0 driver. Copy it back to the install directory once the installation
is complete.
Refer to TLS/SSL server authentication and TLS/SSL client authentication for details.
- 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 has been enhanced to support the Windows certificate store for TLS/SSL server authentication. Refer to the TLS/SSL server authentication for details.*
- The driver has been enhanced to support TLS/SSL server authentication for the applications deployed in a serverless environment. The driver stores the TLS/SSL certificates in memory and lets applications use TLS/SSL server authentication without storing
the truststore file on the disk. To use this enhancement, specify the content of the certificate in the refreshed Trust Store (Truststore) connection option or the new SQL_COPT_INMEMORY_TRUSTSTORECERT pre-connection attribute. Refer to Trust Store and Using SQL_COPT_INMEMORY_TRUSTSTORECERT for details.*
- The Batch Mechanism (BatchMechanism) connection option has been enhanced to support the native batch protocol for batch inserts. When BatchMechanism is set to 4 (NativeBatch), the driver uses the native batch protocol for the insert
operation of all batched parameters. For update and delete batch operations, the driver uses the native batch mechanism by default to handle the request. Refer to Batch Mechanism for details.*
- The Use Declare Fetch (UseDeclareFetch) and Fetch Size (FetchSize) connection options have been added to the driver. The Use Declare Fetch option determines whether the driver attempts to return a result set in a single fetch or across multiple fetches.
If multiple fetches are used, the setting of the Fetch Size option determines the size of each fetch. For large result sets, retrieving rows in multiple fetches can improve response time and thereby prevent possible timeouts. Refer to the user's
guide for details. See Use Declare Fetch and Fetch Size 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.*
- The driver has been enhanced to support stored procedures for PostgreSQL 11 and later.
- The Call Escape Behavior (CallEscapeBehavior) connection option has been added to the driver. The driver determines whether to call a user-defined function or a stored procedure based on the value specified for this option. Refer to Call Escape Behavior for details.
- The driver has been enhanced to support certificate-based authentication. It uses TLS/SSL protocol for authentication and authenticates the client to the server if the TLS/SSL client certificate is issued by a trusted Certificate Authority (CA) and
the Common Name (cn) attribute of the TLS/SSL client certificate matches the database user name. Two new connection options, Client SSL Certificate and Client SSL Key, have been added to support this authentication method. Refer to the Certificate-based authentication for details.
- The Show Selectable Tables (ShowSelectableTables) connection option has been added to the driver. It determines whether the driver returns metadata for all tables or only for the tables for which the user has Select privileges. It can help the users
with restricted Select privileges retrieve metadata for the required tables. Refer to Show Selectable Tables for details.
- The driver has been enhanced to support the SCRAM-SHA-256-PLUS authentication method, which uses channel binding for establishing a secure connection with PostgreSQL (v11.0 and higher).
- The driver has been enhanced with the new Batch Mechanism (BatchMechanism) connection option, which specifies the preferred mechanism for executing batch insert operations. By setting Batch Mechanism to 2 (MultiRowInsert) or 3 (Copy), the driver can
achieve substantial performance gains when performing batch inserts. Refer to the Batch Mechanism for details.
- The driver has been enhanced to support the following data types: Citext, Float, and Tinyint. See Data Types for details.
- The drivers using base version B0649 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.
This enhancement is available in build 07.16.0398 of the driver manager.
- A Power BI connector is now included with the product package. You can use this connector to access your PostgreSQL data with Power BI. Refer to the Power BI (Windows only) for details.
- The driver has been enhanced to support Select queries with parameterized arrays.
- The driver has been enhanced to support md5 and scram-sha-256 authentication methods.
- The driver has been enhanced to support materialized views and foreign tables.
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.
- For PostgreSQL 9.0 and later, the driver behavior has been updated to support executing multiple prepared statements in a single query that contain inserts for BYTEA values. However, for versions earlier than PostgreSQL 9.0, this functionality is
not supported and the driver returns an error.
- The default value for the Batch Mechanism (BatchMechanism) connection option has been changed to 3 (Copy). The driver now, by default, uses the PostgreSQL COPY command to insert rows into the target table. It allows the driver to achieve substantial
performance improvements over 1 (SingleRowInsert) when performing batch inserts. Refer to the user's guide for details. Refer to Batch Mechanism for details.
Version 7.1.6
Enhancements
- The default version of the OpenSSL library has been upgraded to version 1.1.1k, which fixes the following security vulnerabilities:*
- CA certificate check bypass with X509_V_FLAG_X509_STRICT (CVE-2021-3450)
- NULL pointer deref in signature_algorithms processing (CVE-2021-3449)
- Null pointer deref in X509_issuer_and_serial_hash() (CVE-2021-23841)
- Integer overflow in CipherUpdate (CVE-2021-23840)
Version 1.1.1k also addresses vulnerabilities resolved by earlier versions of the library. For more information on the installed library files, refer to the readme.
For more information on the OpenSSL vulnerabilities resolved by this upgrade,
refer to the corresponding OpenSSL announcements at
https://www.openssl.org/news/vulnerabilities-1.1.1.html.
- OpenSSL library 1.1.1i has been replaced with version 1.1.1k. In addition to fixing multiple new vulnerabilities, version 1.1.1k also addresses the vulnerability resolved by version 1.1.1i: Incorrect behavior of the GENERAL_NAME_cmp function (CVE-2020-1971).*
- OpenSSL library version 1.1.1g has been replaced with version 1.1.1k. In addition to fixing multiple new vulnerabilities, version 1.1.1k also addresses the vulnerabilities resolved by version 1.1.1k:*
- Segmentation fault in SSL_check_chain (CVE-2020-1967)
- rsaz_512_sqr overflow bug on x86_64 (CVE-2019-1551)
- OpenSSL library 1.0.2r has been replaced with version 1.0.2u. In addition to fixing multiple new vulnerabilities, version 1.0.2u also addresses the vulnerabilities resolved by version 1.0.2r.*
Version 1.0.2u of the OpenSSL library fixes the following
security vulnerabilities:
- x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli (CVE-2019-1563)
- Padding Oracle in PKCS7_dataDecode and CMS_decrypt_set1_pkey (CVE-2019-1563)
- Compute ECC cofactors if not provided during EC_GROUP construction (CVE-2019-1547)
- Installation paths in diverse Windows builds (CVE-2019-1552)
Note: By default, the driver will attempt to load version 1.1.1 of the library; however, if the library cannot be loaded, the driver will fall back to version 1.0.2.
- The default OpenSSL library version has been updated to 1.1.1d.*
- The default OpenSSL library version has been updated to 1.0.2r:*
- The default OpenSSL library version has been updated to 1.0.2n.*
- The default OpenSSL library version has been updated to 1.0.2k.*
- The default OpenSSL library version has been updated to 1.0.2j.*
- The default OpenSSL library version has been updated to 1.0.2h.*
- The default OpenSSL library version has been updated to 1.0.2g.*
- The default OpenSSL library version has been updated to 1.0.2f.
- Support for Kerberos Authentication.
- The new CryptoLibName and SSLLibName connection options allow you to
designate the OpenSSL libraries used when SSL is enabled.
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 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. - The new Unbounded Numeric Precision connection option allows you to
define the precision for unbounded NUMERIC columns described
within the column, parameter, result set, or table metadata. - The new Unbounded Numeric Scale connection option allows you to
define the scale for unbounded NUMERIC columns described within
the column, parameter, result set, or table metadata.
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
Changed Behavior
- The EncryptionMethod connection option now supports Request SSL
functionality. When Request SSL is enabled, login requests and data are
encrypted if the server is configured for SSL. If the server is not
configured for SSL, an unencrypted
connection is established.
Version 7.1.2
No features introduced
Version 7.1.1
No features introduced
Version 7.1.0
No features introduced
Progress DataDirect for ODBC for Teradata Driver
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:
Version 8.0.2
Enhancements
- The driver is upgraded to the 8.0 framework, thereby, ensuring that the base components stay aligned with the latest security fixes and enhancements.
- The driver is built using the CLIv2 library. The minimum CLIv2 library versions required for compatibility with the driver are as follows:
- Windows - v17.20
- Linux - v17.20
- AIX - v17.20
- Solaris - v16.20
- HP - v16.20
Changed Behavior
- 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.
- The following operating systems are no longer supported:
- AIX 32 Bit
- Solaris.Sparc32
Version 7.1.6
Enhancements
- Some components of the driver are now compiled with a 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.*
- 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). - 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.*
- The drivers using base version B0649 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.
This enhancement is available in build 07.16.0398 of the driver manager.
- The driver has been enhanced to support the Number data type. Refer to Data types 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.
Version 7.1.5
No features introduced
Version 7.1.4
No features introduced
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
Progress DataDirect for ODBC for SAP S/4HANA
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:
Version 8.0.1
Enhancements
- The driver is now compiled with a Visual Studio 2022 compiler for the 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 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 has been enhanced to support SAP BW/4HANA and other SAP ODATA V2 services exposed through the SAP NetWeaver Gateway. Refer to Supported SQL statements and extensions for details.
- The driver has been enhanced to support CDS views that require parameters. Refer to CDS views for details.
- The driver has been enhanced to support HTTP Header authentication for use with the S/4HANA sandbox hosted at https://api.sap.com. Refer to HTTP header authentication for details.
- The driver has been enhanced to determine the maximum size of VARCHAR columns within the result set metadata using the new Maximum Varchar Size connection option. Refer to Maximum Varchar Size 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.*
- The driver has been enhanced to support a default value of 100000 for the Web Service Fetch Size connection option. Refer to Web Service Fetch Size for details.
- The curl library files that are installed with the product have been upgraded to version 7.75.0, which fixes a number of potential security vulnerabilities. For more information on the vulnerabilities resolved by this enhancement, refer to:
https://curl.haxx.se/docs/vulnerabilities.html. This upgrade is available starting in build 08.02.0239 of the curl library files.
Changed Behavior
Version 8.0.0
Features
Progress DataDirect for ODBC for Apache Cassandra Driver
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:
Version 8.0.0
Enhancements
- The driver is now compiled with a Visual Studio 2022 compiler for the 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.
- 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. 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.*
- 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 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.*
- For Linux platforms, 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 on Linux, the ICU file name has changed from libivicu28.so to libivicu.so. For the 64-bit driver on Linux, the ICU file name has changed from libddicu28.so to libddicu.so. This upgrade does not apply to UNIX platforms. This upgrade is available starting in build 08.02.0965 of the ICU library files.*
- 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.*
- 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 has been enhanced to allow you to configure how collections are mapped in the relational view of your data. By configuring the new Schema Format (SchemaFormat) config option, you can determine whether the driver normalizes collections and collections labeled FROZEN. Refer to SchemaFormat (config option) for details.
- The driver has been enhanced to support connection failover and client load balancing when connecting to a cluster. You can enable this new functionality by specifying a comma-separated list of member nodes using the new Cluster Nodes (ClusterNodes) connection option. Refer to Using failover in a cluster and Cluster Nodes for details.
Available in driver version 08.00.0216 (B0706, U0505, J000324) - The drivers using base version B0649 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 has been enhanced to support the Duration data type, which maps to the SQL_VARCHAR ODBC type. Currently, the Duration type is supported only in simple columns, and not in Collection types. Refer to Data types for details.*
- 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.
This enhancement is available in build 08.02.0449 of the driver manager.
- The driver has been enhanced to support all the data consistency levels for read and write operations that are supported by Apache Cassandra data stores. Data consistency levels are configured using the Read Consistency and Write Consistency connection options. Refer to the user's guide and reference for descriptions of these options. Refer to Read Consistency and Write Consistency for details.*
Changed Behavior
Features
- Supports SQL read-write access to Apache Cassandra data sources. Refer to Supported SQL functionality for details.
- Supports CQL Binary Protocol.
- The driver supports the core SQL-92 grammar.
- The driver supports all ODBC Core functions and some Level 1 and Level 2 features. Refer to ODBC compliance for details.
- Supports user id and password authentication. Refer to Authentication Method for details.
- Supports Cassandra data types, including the complex types Tuple, user-defined types, Map, List and Set. Refer to Data types for details.
- Generates a normalized view of Cassandra data. Tuple and user-defined types are flattened into a relational parent table, while collection types are mapped as relational child tables. Refer to Complex type normalization for details.
- Supports Native and Refresh escape sequences to embed CQL commands in SQL-92 statements. Refer to Native and Refresh escape clauses for details.
- Supports Cassandra's tunable consistency functionality with the ReadConsistency and WriteConsistency connection options. Refer to Read Consistency and Write Consistency for details.
- Supports the handling of large result sets through the FetchSize, NativeFetchSize, and ResultMemorySize connection options. Refer to Fetch Size, Native Fetch Size, and Result Memory Size for details.
- Supports applications that do not support unbounded data types through the ASCIISize, DecimalPrecision, DecimalScale, VarintPrecision, and VarcharSize connection options. Refer to Ascii Size, Decimal Precision, Decimal Scale, Varchar Size, and Varint Precision for details.
Progress DataDirect for ODBC for HubSpot
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:
Version 8.0.0
ENHANCEMENT
- 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.*
Changed Behavior
Features
- The driver supports SQL read-only access to HubSpot. 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 HubSpot data types through data type inference. Refer to Data types for details.
- The driver supports OAuth 2.0 authentication. Refer to OAuth 2.0 authentication for details.
- The driver supports API key authentication. Refer to API key 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 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
- Fetch OAuth tokens and configure OAuth
- Access connection option 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.
- 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.
Progress DataDirect for ODBC for Microsoft Dynamics 365
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:
Version 8.0.0
Enhancements
- The driver is now compiled with a Visual Studio 2022 compiler for the 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 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 driver has been enhanced to support fetching data from all the companies to which the user has access. Earlier, the driver supported fetching data only from the default company of the user. You can configure this functionality using the new Cross
Company (CrossCompany) connection option. Refer to Cross Company for more information.*
- Available: Driver version 8.0.0.1485 (B1227, U1070)-J2178
- 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 has been enhanced to allow you to configure whether requests to web services timeout when the service is unresponsive. You can configure this functionality using the new Web Service Timeout (WSTimeout) connection option. Refer to Web Service Timeout for more information.*
- 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
Features
- The driver supports SQL read-write access to the following Microsoft Dynamics 365 apps:
- CRM apps
- Customer Service
- Field Service
- Marketing
- Project Service Automation
- Sales
- ERP apps
- Finance
- Retail
- Supply Chain Management
- Talent
Refer to Supported SQL statements and extensions for more information.
- 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 OAuth 2.0 authentication. Refer to OAuth 2.0 authentication for supported grant types and further details.
- The driver supports NTLM authentication. Refer to NTLM 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.
- The driver supports optimizing insert, update, and delete operations with the Batch Update Chunk Size (BatchUpdateChunkSize) connection option. Refer to Batch Update Chunk Size for details.
- On Windows platforms, the driver includes 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 URLs
- Test connect data sources and connection URLs
- Execute SQL commands for testing;
- Fetch OAuth tokens
- 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.
Progress DataDirect for ODBC for GitHub
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:
Version 8.0.0
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 has been enhanced to support the Bearer token authentication method. Refer to Bearer token authentication 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
FEATURES
Progress DataDirect for ODBC for Apache Spark SQL
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:
Version 8.0.2
Enhancements
- The driver is now compiled with a Visual Studio 2022 compiler for the 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.
- 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. 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.*
- 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 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.*
- For Linux platforms, 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 on Linux, the ICU file name has changed from libivicu28.so to libivicu.so. For the 64-bit driver on Linux, the ICU file name has changed from libddicu28.so to libddicu.so. This upgrade does not apply to UNIX platforms. This upgrade is available starting in build 08.02.0965 of the ICU library files.*
- Note: OpenSSL library 3.0.9 has been replaced with a later version. For the latest information about the third-party components that are installed with the product, refer to the Third-party Components Compatibility Matrix.
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 8.0 drivers, upgrade all your drivers to the latest version.
- If you are using both 8.0 and 7.1 versions of the driver, copy the xxtls27.dll/libxxtls27.so[.sl] file to a different location before installing a new version of the 8.0 driver. Copy it back to the install directory once the installation
is complete.
Refer to TLS/SSL server authentication and TLS/SSL client authentication for details.
- The driver has been enhanced to allow you to override the default value of the User-Agent header when required by a service. Using the new User Agent (UserAgent) option, you can specify the string value of the User-Agent header to be used in HTTP requests. Refer to User Agent 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.*
- The driver has been enhanced to support connections to Azure Databricks Spark clusters. Refer to Azure Databricks Spark clusters for details.
- The driver has been enhanced to support HTTP mode, which allows you to access Apache Hive data stores using HTTP/HTTPS requests. HTTP mode can be configured using the new Transport Mode and HTTP Path connection options. Refer to HTTP mode, Transport Mode, and HTTP Path for details.*
- The driver has been enhanced to support session cookie based authentication for HTTP connections. Cookie based authentication can be configured using the new Enable Cookie Authentication and Cookie Name connection options. See Enable Cookie Authentication, and Cookie Name.*
- The drivers using base version B0649 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. Refer to Driver Manager and Unicode encoding on UNIX/Linux in the Progress DataDirect for ODBC Drivers Reference for details.*
This enhancement is available in build 08.02.0449 of the driver manager.
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.
Version 8.0.1
Enhancements
- The driver has been enhanced to support the Decimal and Varchar data types.
- The new Min Long Varchar Size connection option allows you to fetch SQL_LONGVARCHAR columns whose size is smaller than the minimum imposed by some third-party applications, such as SQL Server Linked Server.
- The new Varchar Threshold connection option allows you to fetch columns that would otherwise exceed the upper limit of the SQL_VARCHAR type for some third-party applications, such as SQL Server Linked Server.
Version 8.0.0
Features
- Support for Apache Spark SQL
- DataDirect Wire Protocol technology for improved response time and throughput.
- Support for all ODBC Core and Level 1 functions.
- Support for core SQL-92 grammar.
- Advanced security features, including:
- Kerberos authentication
- Data encryption
Progress DataDirect for ODBC for Aha
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:
Version 8.0.0
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.*
- 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
Features
- The driver supports SQL read-only access to Aha!. 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 for details.
- The driver supports Aha! data types through data type inference. Refer to Data types for details.
- The driver supports Aha! custom fields, including many fields added through third-party plug-ins.
- The driver supports OAuth 2.0 authentication. Refer to OAuth 2.0 authentication for details.
- The driver supports basic user id and password authentication. Refer to Basic authentication for details.
- The driver supports URL parameter (API key) authentication. Refer to URL parameter (API key) authentication for details.
- The driver supports the handling of large result sets with paging, and the Fetch Size (FetchSize) and Web Services Fetch Size (WSFetchSize) connection options. Refer to Fetch Size and Web Service Fetch Size for details.
- On Windows platforms, the driver includes the DataDirect ODBC Driver Configuration Manager for quick configuration and testing of your driver. This Configuration Manager allows you to: