Support and Certifications

Visit the following web pages for the latest support and certification information.

Changes Since 8.0.2 GA

  • Driver Enhancements
    • The default version of the OpenSSL library has been upgraded to 3.5.6. As part of this upgrade, earlier version of the OpenSSL 3.0 library continues to be supported to provide the best protection for your data. The upgrade is available in the following OpenSSL library files:
      • Windows: ivopenssl.dll and ddopenssl.dll
      • Unix: ivopenssl.so and ddopenssl.so
    • The driver now provides read-write access to the Synapse Data Warehouse endpoints of Microsoft Fabric. For connection string examples, limitations, and configuration settings for warning messages, see Connection string examples, Support for Microsoft Fabric and SuppressFabricWarnings.
    • 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 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 and AE Keystore Secret connection options. See Using keystore providers for details.
    • 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.
    • 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.
    • 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.
    • The default version of the OpenSSL library has been upgraded to 3.0. As part of this upgrade, earlier versions of the OpenSSL library are no longer supported to provide the best protection for your data. The upgrade is available in the following OpenSSL library files: xxopenssl30.dll (for Windows) and xxopenssl30.so [.sl] (for UNIX/Linux).

      The OpenSSL 3.0 library uses a set of shared libraries called providers to implement different types of cryptographic algorithms. The driver supports the following OpenSSL 3.0 providers: FIPS and default. See TLS/SSL server authentication and TLS/SSL client authentication for details.

    • The driver has been enhanced to support the Windows certificate store for TLS/SSL server authentication. See 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. See Trust Store and Using SQL_COPT_INMEMORY_TRUSTSTORECERT 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 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. See Keep Connection Active and Socket Idle Time for details.
    • The driver supports inserts into IDENTITY columns in data replication scenarios. The Enable Replication User connection option (EnableReplicationUser) or the SQL_COPT_REPLICATION_USER connection attribute (numeric value 1080) can be used to allow inserts into IDENTITY columns defined as NOT FOR REPLICATION. For details, see Inserts on IDENTITY columns in data replication scenarios and Enable Replication User.
    • The driver has been enhanced to support distributed transactions. It implements the XA interface to enable support for distributed transactions. For details, see XA interface support.
    • The driver is enhanced to support access token authentication programmatically with the use of a pre-connection SQL_COPT_SS_ACCESS_TOKEN attribute. See Access token authentication 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.

      Refer to Driver Manager and Unicode encoding on UNIX/Linux in Progress DataDirect for ODBC Drivers Reference for details.

      This enhancement is available in build 08.02.0449 of the driver manager.

    • 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. See Always Encrypted for details.
  • Changed Behavior
    • Microsoft has rebranded Azure Active Directory as Microsoft Entra ID. As a result, the driver documentation has been updated to reflect this name change.
    • 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. See Crypto Protocol Version for more information.
    • The Allowed OpenSSL Versions (AllowedOpenSSLVersions) connection option has been deprecated.
    • 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. Therefore, if you are using multiple drivers, upgrade all your drivers to the latest version.
    • 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 crypto protocol versions prior to TLSv1 are no longer supported.

    • When executing SQLGetInfo(SQL_COLLATION_SEQ), the driver now fetches the collation sequence from the server. Earlier, it always returned ISO 8859-1 as the collation sequence.

    • 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 following Windows platforms have reached the end of their product lifecycle and are no longer supported by the driver:
      • Windows 8.0 (versions 8.1 and higher are still supported)
      • Windows Vista (all versions)
      • Windows XP (all versions)
      • Windows Server 2003 (all versions)

Changes for 8.0.2 GA

  • Platform Certifications
    • Certified with Red Hat Enterprise 7.3
    • Certified with Debian 7.11, 8.5
    • Certified with Ubuntu 14.04, 16.04
    • Certified with Windows Server 2016
  • Data Source Version Certifications
    • Certified with Microsoft Azure Synapse Analytics 12.00
    • Certified with Microsoft Analytics Platform System 10.00
    • Certified with Microsoft SQL Server 2016, 2017
  • Driver Enhancements
    • The driver has been enhanced to transparently connect to Microsoft Azure Synapse Analytics and Microsoft Analytics Platform System data sources. See Support for Azure Synapse Analytics and Analytics Platform System for more information about supported features and functionality.
    • 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. See Proxy Host, Proxy Mode, Proxy Password, Proxy Port, and Proxy User for details.
    • The new Enable Server Side Cursors connection option allows you to determine which server-side cursors are enabled for the data source. See Enable Server Side Cursors for details.
    • The driver is enhanced to support Microsoft Entra ID authentication using user names and passwords. Entra ID authentication is an alternative to SQL Server Authentication for Azure SQL Database that allows you to centrally manage identities of database users. See Microsoft Entra ID 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 new Multi-Subnet Failover 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. To support high availability with Always On, this option must be enabled.
      • 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.
      See 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 Progress DataDirect for ODBC Drivers Reference for details.

  • Changed Behavior
    • The default value for Crypto Protocol Version has been updated to TLSv1.3,TLSv1.2. This change improves the security of the driver by employing only the most secure cryptographic protocols as the default behavior. See Crypto Protocol Version for details.
    • 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. See Crypto Protocol Version for details.