![]() |
VOOZH | about |
MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData ODBC Driver for Lakebase, you gain database-like access to live Lakebase data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through adding Lakebase as external data in MicroStrategy Web and creating a simple visualization of Lakebase data.
The CData ODBC driver offers unmatched performance for interacting with live Lakebase data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to Lakebase, the driver pushes supported SQL operations, like filters and aggregations, directly to Lakebase 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 Lakebase data using native MicroStrategy data types.
Information for connecting to Lakebase follows, along with different instructions for configuring a DSN in Windows and Linux environments (the ODBC Driver for Lakebase must be installed on the machine hosting the connected MicroStrategy Intelligence Server).
To connect to Databricks Lakebase, start by setting the following properties:To authenicate using OAuth client credentials, you need to configure an OAuth client in your service principal. In short, you need to do the following:
For more information, refer to the Setting Up OAuthClient Authentication section in the Help documentation.
To authenticate using the OAuth code type with PKCE (Proof Key for Code Exchange), set the following properties:
For more information, refer to the Help documentation.
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 Lakebase 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 Lakebase Sys] Driver = CData ODBC Driver for Lakebase Description = My Description DatabricksInstance = lakebase Server = 127.0.0.1 Port = 5432 Database = my_database InitiateOAuth = GETANDREFRESH
For specific information on using these configuration files, please refer to the help documentation (installed and found online).
Once you have created a database instance in MicroStrategy Developer and connected it to a project, you can perform a data import of Lakebase data from MicroStrategy Web. Alternatively, you can create a new data source based on the ODBC Driver.*
SELECT CatalogName NAME_SPACE, TableName TAB_NAME FROM SYS_TABLES
SELECT DISTINCT CatalogName NAME_SPACE, TableName TAB_NAME, ColumnName COL_NAME, DataTypeName DATA_TYPE, Length DATA_LEN, NumericPrecision DATA_PREC, NumericScale DATA_SCALE FROM SYS_TABLECOLUMNS WHERE TableName IN (#TABLE_LIST#) ORDER BY 1,2,3
Using the CData ODBC Driver for Lakebase in MicroStrategy Web, you can easily create robust visualizations and reports on Lakebase data. Read our other articles on connecting to Lakebase in MicroStrategy and connecting to Lakebase in MicroStrategy Desktop for more examples.
Note: connecting using a ODBC driver requires a 3- or 4-tier architecture.
Download a free trial of the Lakebase ODBC Driver to get started:
Download NowLearn more:
๐ Lakebase IconThe Lakebase ODBC Driver is a powerful tool that allows you to connect with live data from Lakebase, directly from any applications that support ODBC connectivity.
Access Lakebase data like you would a database - read, write, and update Lakebase 0, etc. through a standard ODBC Driver interface.