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

Refer to the following resources for additional information:

• Product Compatibility Guide: Provides the latest data source and platform support information. 
• Fixes: Describes the issues resolved since general availability.  

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.*
  Available: 3/19/2024 | 08.00.0402.
• The driver has been enhanced to retry API call executions when an HTTP failure or driver exception occurs. You can configure this behavior with the new Retry Exceptions (RetryExceptions) connection option. When this option is set to 1, the driver uses the retry value specified by the WS Retry Count (WSRetryCount) connection option.*
  Available: 11/22/2023 | 08.00.0357.
• The driver has been enhanced to support fetching access and refresh tokens at connection when OAuth2.0 is enabled. When using the new dynamic authorization code grant, you can initiate an authorization code grant flow by specifying login credentials using the login prompt for your service, thereby providing a method to authenticate without fetching access and refresh tokens via the Configuration Manager or a third-party application. In addition, the new Enable Login Prompt (EnableLoginPrompt) and Redirect URI (RedirectURI) options have been added to enable this functionality.*
  Available: 11/22/2023 | 08.00.0357.
• The driver has been enhanced to support the JSON and Interval data types, which map to the SQL_LONGVARCHAR and SQL_VARCHAR ODBC data types respectively.*
  Available: 11/22/2023 | 08.00.0357.
• On Windows platforms, the driver includes an enhanced setup dialog, the Progress DataDirect Google BigQuery Configuration Manager, for quick configuration and testing of your driver in a web browser. The tool allows you to:
  • Configure data sources
  • Generate and edit connection strings
  • Test connect data sources and connection strings
  • Execute SQL commands for testing
  • Access connection option descriptions and the full product documentation*

  Available: 11/22/2023 | 08.00.0357

• The driver has been enhanced to support the Google BigQuery Streaming API for executing batch inserts. The Use Streaming Insert connection option has been added to the driver. This option is enabled by default. Refer to Google BigQuery Streaming API 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 allow users to specify values for the following exposed connection options:
  • Auth URI and Token URI for OAuth 2.0 authentication.
  • JWT Audience and Token URI for Service Account authentication.
  Previously, the driver used the default values for these options when authenticating to Google BigQuery. Refer to Configuring OAuth 2.0 authentication and Configuring service account 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 fetch metadata for multiple tables parallelly at connection time. This enhancement provides performance benefits when connecting to a dataset that has a large amount of data.*
• The driver has been enhanced to support the BIGNUMERIC data type, which maps to the SQL_DECIMAL ODBC data type. Refer to Data types for more information.*
• The Service Account Key Content connection option has been added to the driver. This option allows you to specify the private key required for service account authentication without having to persist the .json or .p12 file that contains the private key (as required with the Service Account Private Key option). Refer to Configuring service account authentication and Service Account Key Content for details.*
• The Enable Catalog Support connection option has been added to the driver. It determines whether the driver supports specifying values for catalog parameters in metadata calls. Note that catalogs and schemas are equivalent to projects and datasets in Google BigQuery. Refer to Enable Catalog Support 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 Packet Logging Options=1. The internal packet logging is not enabled by default. To enable it, set EnablePacketLogging=1.*
• The driver has been enhanced to support the Google BigQuery Storage API when fetching large result sets. Refer to Google BigQuery Storage API and Storage API attributes for details.*
  Note: Currently, the Storage API is supported only on Windows 64-bit, Linux 64-bit, and JVM 64-bit. If an application attempts to use the Storage API on an unsupported platform, the driver falls back to the Standard API. 
• 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.

CHANGED BEHAVIOR

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

  Notes:

  • This change does not affect the JVM requirements for the driver. For the latest driver requirements, refer to the Product Compatibility Guide.
  • The installer program cannot remove the already installed JRE files from the install directory automatically. Remove them manually.
  • To install the 32-bit drivers on 64-bit Windows platforms and start the SQL engine service, the installer requires the 32-bit version of Java SE 11 or higher installed on your machine and defined on your path.
• The product package no longer includes the ODBC Cursor library file (odbccurs.so) because it has some known security vulnerabilities that could potentially expose you to security risks.*
  Note: The installer program cannot remove the ODBC Cursor library file automatically while installing a new version of the driver. Remove it manually.
• The installer program has been updated to no longer install common components for drivers that do not use them. As a result, the installer program no longer installs the following common components for the Google BigQuery 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.

• The driver updates string values in an existing DSN to number values when the Configuration Manager is used to update the Authentication Method (AuthenticationMethod) connection option. The following updates occur:
  • The string value "oauth2.0" is updated to 24
  • The string value "serviceaccount" is updated to 28*
• When existing DSNs are updated using the Configuration Manager, the Boolean values of "0" and "1" are converted to "true" and "false" for relevant connection options.*
• On Windows platform, the default value of the SQL Engine Mode (SQLEngineMode) connection option has been changed to 1 (Server). 
• The default value of the Schema Set (SchemaSet) configuration option has been changed to the project and dataset specified at connection. Refer to SchemaSet (Config Option) for details.*
• The default value of the WS Retry Count (WSRetryCount) connection option has been changed to 5.*

FEATURES

• Supports standard and legacy Google BigQuery SQL dialects. Refer to Standard and legacy SQL support for more information.
• Serves as a complete pass-through driver that leverages Google BigQuery SQL engine to execute queries.
• Supports create, read, update, and delete (CRUD) operations.
  
• Returns data for complex data types, such as Array and Struct, as JSON strings, in a format that is easy to comprehend for ODBC applications. Refer to Json Format for more information.
• Supports proxy connections. Refer to Connecting through a proxy server for more information.
• Supports the handling of large result sets with configurable paging and the Fetch Size and WS Fetch Size connection options.