![]() |
VOOZH | about |
MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When paired with the CData ODBC Driver for Databricks, you gain database-like access to live Databricks data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through adding Databricks as a data source in MicroStrategy Desktop and creating a simple visualization of Databricks data.
The CData ODBC Driver offers unmatched performance for interacting with live Databricks data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to Databricks, the driver pushes supported SQL operations, like filters and aggregations, directly to Databricks and utilizes the embedded SQL Engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze Databricks data using native MicroStrategy data types.
Accessing and integrating live data from Databricks has never been easier with CData. Customers rely on CData connectivity to:
While many customers are using CData's solutions to migrate data from different systems into their Databricks data lakehouse, several customers use our live connectivity solutions to federate connectivity between their databases and Databricks. These customers are using SQL Server Linked Servers or Polybase to get live access to Databricks from within their existing RDBMs.
Read more about common Databricks use-cases and how CData's solutions help solve data problems in our blog: What is Databricks Used For? 6 Use Cases.
Information for connecting to Databricks follows, along with different instructions for configuring a DSN in Windows and Linux environments.
To connect to a Databricks cluster, set the properties as described below.
Note: The needed values can be found in your Databricks instance by navigating to Clusters, and selecting the desired cluster, and selecting the JDBC/ODBC tab under Advanced Options.
When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
If you are installing the CData ODBC Driver for Databricks in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.
[CData Databricks Sys] Driver = CData ODBC Driver for Databricks Description = My Description Server = 127.0.0.1 Port = 443 TransportMode = HTTP HTTPPath = MyHTTPPath UseSSL = True User = MyUser Password = MyPassword
For specific information on using these configuration files, please refer to the help documentation (installed and found online).
In addition to connecting Databricks in MicroStrategy enterprise products, you can connect to Databricks in MicroStrategy Desktop. Follow the steps below to add Databricks data as a dataset and create visualizations and reports of Databricks data.
SELECT * FROM Customers👁 Querying Databricks for data.
Using the CData ODBC Driver for Databricks in MicroStrategy Desktop, you can easily create robust visualizations and reports on Databricks data. Read our other articles on connecting to Databricks in MicroStrategy and connecting to Databricks in MicroStrategy Web for more examples.
Download a free trial of the Databricks ODBC Driver to get started:
Download NowLearn more:
👁 Databricks IconThe Databricks ODBC Driver is a powerful tool that allows you to connect with live data from Databricks, directly from any applications that support ODBC connectivity.
Access Databricks data like you would a database - read, write, and update through a standard ODBC Driver interface.