Use the CData JDBC Driver for Lakebase in MicroStrategy Desktop

MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData JDBC 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 a data source in MicroStrategy Desktop and creating a simple visualization of Lakebase data.

The CData JDBC 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 use native MicroStrategy data types to visualize and analyze Lakebase data.

Connect to and Visualize Lakebase Data using MicroStrategy Desktop

In addition to connecting to Lakebase in MicroStrategy enterprise products, you can connect to Lakebase in MicroStrategy Desktop. Follow the steps below to add Lakebase data as a dataset using JDBC and create visualizations and reports of Lakebase data.

1. Open MicroStrategy Desktop and create a new dossier.
2. In the datasets panel, click New Data, select Databases, and choose Select a Table as the Import Option.
3. Add a new data source and choose the DSN-less data sources option.
4. Choose Generic in the Database menu and Generic DBMS in the Version menu.
5. Click the link to show the connection string and opt to edit the connection string. In the Driver menu, select MicroStrategy Cassandra ODBC Driver. (MicroStrategy requires a certified driver to interface through JDBC; the actual driver will not be used.)
6. Set the connection string as follows and click OK:
   • Add the JDBC keyword to the connection string.
   • Set MSTR_JDBC_JAR_FOLDER to the path of the JAR file for the JDBC driver. (C:\Program Files\CData JDBC Driver for Lakebase\lib\ on Windows.)
   • Set DRIVER to cdata.jdbc.lakebase.LakebaseDriver, the driver class.
   • Set URL to the JDBC URL for the Lakebase driver, setting the necessary connection properties. To connect to Databricks Lakebase, start by setting the following properties:
     • DatabricksInstance: The Databricks instance or server hostname, provided in the format instance-abcdef12-3456-7890-abcd-abcdef123456.database.cloud.databricks.com.
     • Server: The host name or IP address of the server hosting the Lakebase database.
     • Port (optional): The port of the server hosting the Lakebase database, set to 5432 by default.
     • Database (optional): The database to connect to after authenticating to the Lakebase Server, set to the authenticating user's default database by default.

     OAuth Client Authentication

     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:

     1. Create and configure a new service principal
     2. Assign permissions to the service principal
     3. Create an OAuth secret for the service principal

     For more information, refer to the Setting Up OAuthClient Authentication section in the Help documentation.

     OAuth PKCE Authentication

     To authenticate using the OAuth code type with PKCE (Proof Key for Code Exchange), set the following properties:

     • AuthScheme: OAuthPKCE.
     • User: The authenticating user's user ID.

     For more information, refer to the Help documentation.

     Built-in Connection String Designer

     For assistance in constructing the JDBC URL, use the connection string designer built into the Lakebase JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

     java -jar cdata.jdbc.lakebase.jar
     

     Fill in the connection properties and copy the connection string to the clipboard.

     

     When you configure the JDBC URL, 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.

   A typical connection string follows:

   JDBC;MSTR_JDBC_JAR_FOLDER=PATH\TO\JAR\;DRIVER=cdata.jdbc.lakebase.LakebaseDriver;URL={jdbc:lakebase:DatabricksInstance=lakebase;Server=127.0.0.1;Port=5432;Database=my_database;InitiateOAuth=GETANDREFRESH;};
   

   
7. Right-click on the new data source, and choose Edit catalog options.
8. Edit the SQL Statement to SELECT * FROM SYS_SCHEMAS to read the metadata from the JDBC Driver.
9. Select the new data source to view the available tables. You may need to manually click the search icon in the Available Tables section to see the tables.
10. Drag tables into the pane to import them. Note: Since we create a live connection, we can import whole tables and utilize the filtering and aggregation features native to the MicroStrategy products.
11. Click Finish and choose the option to connect Live. Live connections are possible and effective, thanks to the high-performance data processing native to CData JDBC Drivers.
12. Choose a visualization, choose fields to display, and apply any filters to create a new visualization of Lakebase data. Data types are discovered automatically through dynamic metadata discovery. Where possible, the complex queries generated by the filters and aggregations will be pushed down to Lakebase, while any unsupported operations (which can include SQL functions and JOIN operations) will be managed client-side by the CData SQL engine embedded in the driver.
13. Once you are finished configuring the dossier, click File -> Save.

Using the CData JDBC Driver for Lakebase in MicroStrategy Desktop, you can easily create robust visualizations and reports on Lakebase data. Read our other articles for connecting to Lakebase data in MicroStrategy Developer and connecting to Lakebase data in MicroStrategy Web for more examples.