Simba ODBC Driver with SQL Connector for Google BigQuery 1.1.11 The release notes provide details of enhancements and features in Simba ODBC Driver with SQL Connector for Google BigQuery 1.1.11, as well as the version history. The following issues have been resolved in Simba ODBC Driver with SQL Connector for Google BigQuery 1.1.11. Driver creates temporary tables for all queries, regardless of result set size Now, the driver only creates temporary tables for queries where the result set size is greater than 128MB. The "Temporary Table Expiration Time" configuration option does not work correctly In some cases, the driver does not handle asynchronous query execution correctly Version History Version 1.1.10 ODBC Driver with SQL Connector for Google BigQuery 1.1.10. Updated the default location of the simba.bigqueryodbc.ini configuration file By default, the simba.bigqueryodbc.ini configuration file is now located in the lib directory corresponding to the bitness of the driver. For example, the configuration file for the 64-bit driver on Linux is located in /opt/simba/bigqueryodbc/lib/64 www.simba.com 1
Updated setup process on non-windows platforms The updated default behavior of the driver is to read the simba.bigqueryodbc.ini file from its new default location in the lib directory. You no longer need to copy the simba.bigqueryodbc.ini configuration file into the home directory. Also, you are no longer required to modify the simba.bigqueryodbc.ini configuration file when setting up the driver on a Linux or Mac OS X machine. The driver can now automatically detect which settings are required in order to work with the ODBC driver manager. SIMBAINI environment variable renamed to SIMBABIGQUERYINI The environment variable for locating the simba.bigqueryodbc.ini configuration file has been renamed from SIMBAINI to SIMBABIGQUERYINI. The default value of SIMBABIGQUERYINI is the default installation location of the simba.bigqueryodbc.ini file. Support added for retrieving metadata during the prepare stage When working in Native Query mode, the driver can now retrieve metadata during the prepare stage of a query. To enable or disable this feature, use the "Enable SQLPrepare Metadata with Native Query" option (the UseNativeQueryMetadata key). Updated logging functionality to improve security Driver logs no longer show the proxy password and refresh token. Updated "Test" functionality in the Windows driver When you click the "Test" button in the DSN Setup dialog box, the driver now checks the license file and reports if it has expired, and also reports some additional driver details. Support added for automatically detecting WinInet proxy settings The driver can now automatically detect the proxy settings to use when connecting through WinInet and set the appropriate values in the DSN Setup dialog box. BigQuery 1.1.10. Mnemonic keys do not work correctly in the Advanced Options dialog box The Proxy Port configuration option does not work correctly www.simba.com 2
Version 1.1.9 ODBC Driver with SQL Connector for Google BigQuery 1.1.9. Version 1.1.8 Updated driver logging options You can now specify the maximum size of each log file by using the "Max File Size" option (the LogFileSize key), and specify the maximum number of log files to keep by using the "Max Number Files" option (the LogFileCount key). Also, in the Logging Options dialog box for the Windows driver, you now have the option of browsing for the folder where you want to save log files instead of typing the path. "Rows Fetched Per Block" option implemented You can now use the "Rows Fetched Per Block" option (the RowsFetchedPerBlock key) to specify the maximum number of rows that the driver can fetch for each data request. Support added for reporting tables and views via SQLTables The driver will now distinguish between tables and views when reporting via SQLTables. ODBC Driver with SQL Connector for Google BigQuery 1.1.8. Updated Connection dialog box The appearance of the Connection dialog box has been modified for consistency with other parts of the user interface. Updated Logging Options dialog box The "Log Namespace" field has been removed from the Logging Options dialog box. Improved handling of SQL queries that do not specify schemas for the tables When processing a query that does not specify the schema to use for the table, the driver will search through every schema and attempt to find a table that matches the table in the query. If multiple schemas contain matching tables, then the query will fail. www.simba.com 3
BigQuery 1.1.8. In specific cases, some ODBC applications retrieve table metadata incorrectly Previously, the problem occurred when the driver reported 0 as the value for SQL_MAX_CATALOG_NAME_LEN, SQL_MAX_COLUMN_NAME_LEN, and SQL_MAX_USER_NAME_LEN. Table metadata can now be retrieved correctly. The data types used by SQLEngine for the metadata between the prepare and execute query stages are different from the data types used by BigQuery Previously, SQLEngine used unsigned data types for the metadata that is generated between the prepare and execute query stages, while BigQuery used signed data types for the same metadata. SQLEngine now uses signed data types. In some cases, when using the driver in SAP Data Services, errors may occur To ensure that the driver works correctly in SAP Data Services, maximum lengths have been set for tables, catalogs, schemas, and columns. Connections to proxy servers do not work correctly The Use Proxy Server setting is not saved correctly in the DSN Now, when you select the Use Proxy Server check box in the DSN Setup dialog box, the setting is saved correctly in the DSN. When converting fractional timestamps to another data type, truncation errors occur Before, the driver added 500 to the fraction, causing truncation errors to occur. Fractional timestamps are now handled correctly. SQLGetTypeInfo reports some incorrect metadata Before, SQLGetTypeInfo incorrectly reported string column lengths, maximum timestamp precision, and the case sensitivity of data types. This metadata is now reported correctly. www.simba.com 4
Version 1.1.7 ODBC Driver with SQL Connector for Google BigQuery 1.1.7. Support added for ODBC 3.80 The driver now supports ODBC 3.80. Third-party libraries statically linked in the Linux and Mac OS X drivers In the Linux and Mac OS X versions of the driver, the third-party libraries are now statically linked. You no longer need to add the lib directory of the driver to the LD_LIBRARY_PATH and DYLD_LIBRARY_PATH environment variables. BigQuery 1.1.7. When the driver is configured to use Native Query Mode, newline characters are included in query strings Version 1.1.6 Newline characters are no longer included in queries. Default setting for Native Query Mode is incorrect Native Query Mode is now disabled by default (the UseNativeQuery key is set to 0). ODBC Driver with SQL Connector for Google BigQuery 1.1.6. Updated DSN Setup dialog box A branding icon has been added to the DSN Setup dialog box, and some minor problems have been fixed. BigQuery 1.1.6. www.simba.com 5
Version 1.1.5 When exiting the DSN Setup dialog box, the driver may terminate unexpectedly ODBC Driver with SQL Connector for Google BigQuery 1.1.5. Updated error messages Error messages in locales other than en-us have been updated. Also, error messages now use "BigQuery" as the component instead of "Gauss". Improved logging functionality Logging now includes information about the internal processes related to the DSN Setup dialog box. Also, the Logging Options dialog box has been modified for ease of use. Support added for large result sets The Google BigQuery API limits result sets to 128 MB in size. You can now configure the driver to handle result sets larger than 128 MB by enabling the Allow Large Result Sets option (setting the AllowLargeResults key to 1). When this feature is enabled, the driver creates a temporary table through the destinationtable parameter of the query job and then uses this temporary table to return the result sets. BigQuery 1.1.5. If internet connectivity is lost while retrieving the refresh token, the DSN Setup dialog box may terminate unexpectedly Version 1.1.4 ODBC Driver with SQL Connector for Google BigQuery 1.1.4. www.simba.com 6
Version 1.1.3 Implemented driver configuration option for specifying the maximum length of String columns You can now specify the maximum length of String columns by setting the Default String Column Length option (the DefaultStringColumnLength key). ODBC Driver with SQL Connector for Google BigQuery 1.1.3. Improved logging of HTTP errors The driver is now better able to log HTTP errors. Support added for configuring logging for each connection Before, driver logging was configured globally so that the settings applied to all connections that used the driver. You can now configure logging differently for each connection by using the following options in the DSN: Log Level (the LogLevel key) Log Path (the LogPath key) Log Namespace (the LogNamespace key) BigQuery 1.1.3. The driver terminates unexpectedly when attempting to process invalid timestamp data If the driver encounters server-side errors when establishing a connection, the connection will fail immediately Version 1.1.2 The driver now retries REST endpoints when server-side errors occur. ODBC Driver with SQL Connector for Google BigQuery 1.1.2. www.simba.com 7
Version 1.1.1 Support added for RTU licensing The driver now supports Right To Use (RTU) licenses. Support added for generating refresh tokens on Linux When using the Linux version of the driver, you can now generate a refresh token from a Google confirmation code by using the new get_refresh_token.sh script. ODBC Driver with SQL Connector for Google BigQuery 1.1.1. Version 1.1.0 Updated driver behavior for loading third-party libraries The driver now loads the libcurl and OpenSSL libraries independently from the application that is loading the driver. ODBC Driver with SQL Connector for Google BigQuery 1.1.0. Linux now supported You can now install and use the driver on computers that run Linux. Updated driver to use SimbaEngine 9.1 The driver now uses SimbaEngine 9.1. Updated driver behavior for handling HTTP requests The driver now uses libcurl instead of WinINet to make HTTP requests. Support added for connecting to a proxy server You can now configure the driver to connect to a proxy server by using the following options: Proxy Host (the ProxyHost key) Proxy Port (the ProxyPort key) Proxy Username (the ProxyUid key) www.simba.com 8
Proxy Password (the ProxyPwd key) BigQuery 1.1.0. Multithreading in the SQL generator does not work correctly www.simba.com 9
Contact Us If you have difficulty using the driver, please contact our Technical Support staff. We welcome your questions, comments and feature requests. Technical Support is available Monday to Friday from 8 a.m. to 5 p.m. Pacific Time. Important: To help us assist you, prior to contacting Technical Support please prepare a detailed summary of the client and server environment including operating system, product version, patch level and configuration. You can contact Technical Support via: E-mail: support@simba.com Web site: www.simba.com Telephone: (604) 633-0008 Extension 3 Fax: (604) 633-0004 You can also follow us on Twitter @SimbaTech www.simba.com 10