Back
Databricks Inc.
Patches for Databricks ODBC Driver x86
Windows
5 patches available
The Simba Apache Spark ODBC Connector is used for direct SQL and HiveQL accessnto Apache Hadoop / Spark distributions, enabling Business Intelligence (BI), analytics,nand reporting on Hadoop-based data. The connector efficiently transforms annapplication’s SQL query into the equivalent form in HiveQL, which is a subset of SQLu000292. If an application is Spark-aware, then the connector is configurable to pass thenquery through to the database for processing. The connector interrogates Spark tonobtain schema information to present to a SQL-based application. Queries, includingnjoins, are translated from SQL to HiveQL.
Databricks ODBC Driver x86 Version 2.11.0.1005
Release Date
3/20/2026
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes
==============================================================================$$$Databricks ODBC Data Connector Release Notes$$$==============================================================================$$$$$$The release notes provide details of enhancements; features; known issues; and$$$workflow changes in Databricks ODBC Connector 2.11.0; as well as the$$$version history.$$$$$$This version of the driver supports the following data source versions and$$$platforms:$$$$$$ * DBR versions 11.3 LTS to 17.3 LTS$$$$$$ * Windows 11; Windows Server 2025; 2022; 2019; 2016; 2012$$$ * macOS 14; 15; 26$$$ * Debian 11$$$ * RHEL 8; 8ARM; 9; 9ARM; 10; 10ARM; AL2023 ARM$$$ * SLES 15$$$ * Ubuntu 22.04; 24.04$$$$$$$$$2.11.0 =======================================================================$$$$$$Release 2026-3-20$$$$$$Enhancements & New Features$$$$$$ * [SPARKO-1658] Stored Procedures$$$$$$ The connector now supports SQL stored procedures when using Databricks$$$ Unity Catalog.$$$$$$ * [SPARKO-1572] Telemetry support$$$$$$ The EnableTelemetry connection setting is on by default. When enabled;$$$ telemetry data will be sent to servers that support this feature.$$$$$$ * [SPARKO-1696] Bulk fetch performance improvement$$$$$$ The connector has improved bulk fetch performance.$$$$$$ * [SPARKO-1677] Geospatial datatype metadata improvement$$$$$$ The connector now returns GEOMETRY or GEOGRAPHY for SQL_DESC_TYPE_NAME$$$ on geospatial data types.$$$$$$ * [SPARKO-1735] macOS 26 support$$$$$$ The connector now support macOS 26.$$$$$$ * [SPARKO-1571] [SPARKO-1737] Updated third-party libraries$$$$$$ The connector now uses the following third-party libraries:$$$ - Expat 2.7.4 (previously 2.7.1)$$$ - OpenSSL 3.0.19 (previously 3.0.18)$$$ - libcURL 8.18.0 (previously 8.16.0)$$$$$$$$$Resolved Issues$$$The following issues have been resolved in Databricks ODBC Connector$$$2.11.0.$$$$$$ * [SPARKO-1646] The DriverConfiguration dialog correctly shows the$$$ connector as Databricks ODBC.$$$$$$$$$Known Issues$$$The following are known issues that you may encounter due to limitations in$$$the data source; the connector; or an application.$$$$$$ * [SPARKO-1404] When querying tables that contain VOID columns; the server$$$ returns an error.$$$$$$ * [SPARKO-1101] When the Auth_AccessToken line length is longer than the$$$ maximum limit of 1000; the connector returns an authentication error. For$$$ more information; see the Installation and Configuration Guide.$$$$$$ * [SPARKO-879] When connecting to a server that supports multiple catalogs;$$$ the connector no longer reports the catalog for schemas and tables as$$$ SPARK.$$$$$$ The Spark server now reports the catalog.$$$$$$ * [SPARKO-670] In some cases; when retrieving timestamp data; the connector$$$ returns an error.$$$$$$ In some cases; when connecting to certain distributions of$$$ Apache Spark; the connector returns the following error: Conversion from$$$ number to string failed due to undersized character buffer. This issue$$$ affects versions 2.6.12 to 2.6.14 of the Spark ODBC connector.$$$$$$ As a workaround; set EnableArrow=0 in the connection string or DSN.$$$$$$ * [SPARKO-620] Issue with date and timestamp before the beginning of the$$$ Gregorian calendar when connecting to Spark 2.4.4 or later; or versions$$$ previous to 3.0; with Arrow result set serialization.$$$$$$ When using Spark 2.4.4 or later; or versions previous to Spark 3.0; DATE$$$ and TIMESTAMP data before October 15; 1582 may be returned incorrectly if$$$ the server supports serializing query results using Apache Arrow. This$$$ issue should not impact most distributions of Apache Spark.$$$$$$ To confirm if your distribution of Spark 2.4.4 or later has been impacted$$$ by this issue; you can execute the following query:$$$$$$ SELECT DATE 1581-10-14$$$$$$ If the result returned by the connector is 1581-10-24; then you are$$$ impacted by the issue. In this case; if your data set contains date and/or$$$ timestamp data earlier than October 15; 1582; you can
Interested in automating patching for Databricks ODBC Driver x86?