Use the CData ODBC Driver for Claude Compliance in MicroStrategy Desktop

MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When paired with the CData ODBC Driver for Claude Compliance, you gain database-like access to live Claude Compliance data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through adding Claude Compliance as a data source in MicroStrategy Desktop and creating a simple visualization of Claude Compliance data.

The CData ODBC Driver offers unmatched performance for interacting with live Claude Compliance data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to Claude Compliance, the driver pushes supported SQL operations, like filters and aggregations, directly to Claude Compliance 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 Claude Compliance data using native MicroStrategy data types.

Connect to Claude Compliance as an ODBC Data Source

Information for connecting to Claude Compliance follows, along with different instructions for configuring a DSN in Windows and Linux environments.

The driver connects to Claude Compliance using a Compliance Access Key, the only supported authentication method. Set the following connection property:

• APIKey: The Compliance Access Key you created.

Creating a Compliance Access Key

1. Enable the Compliance API for your organization.
2. Sign in to claude.ai as a primary owner or organization owner and open Organization settings > API > Keys.
3. Select Create Key and assign only the scopes your integration needs:
   • read:compliance_activities for Activities and the typed activity views.
   • read:compliance_org_data for organizations, roles, groups, and settings.
   • read:compliance_user_data for users, chats, files, projects, and downloads.
   • delete:compliance_user_data for the explicit Delete stored procedures.
4. Create the key and copy it when it appears. The key starts with sk-ant-api01- and is shown only once.

Optionally, set OrganizationUUID to limit organization-scoped views (such as OrganizationUsers and ComplianceRoles) to a single linked organization. If it is left empty, those views default to the first available organization and do not include data from all linked organizations.

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.

Windows

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.

Linux

If you are installing the CData ODBC Driver for Claude Compliance 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.

/etc/odbc.ini

[CData ClaudeCompliance Sys]
Driver = CData ODBC Driver for Claude Compliance
Description = My Description
APIKey = your_compliance_access_key

For specific information on using these configuration files, please refer to the help documentation (installed and found online).

Connect to and Visualize Claude Compliance Data using MicroStrategy Desktop

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

1. Open MicroStrategy Desktop and create a new dossier.
2. In the datasets panel, click New Data, select Databases, and select Type a Query as the Import Option.
3. Add a new data source and choose DSN data sources.
4. Choose the DSN you previously configured (likely CData ClaudeCompliance Sys) and select Generic DBMS in the Version menu.
5. Set the User and Password properties for the DSN (or use placeholder values) and name the data source.

6. Select the new database instance to view the tables. You may need to manually click the search icon in the Available Tables section to see the tables.
7. Create a SQL query for the Claude Compliance data (see below) and click Execute SQL to test the query.

   
   SELECT * FROM Projects
   

   NOTE: Since we create a live connection, we can execute a SELECT * query and utilize the filtering and aggregation features native to the MicroStrategy products.
8. Click Finish and choose to connect live.
9. Choose a visualization, choose fields to display (data types are discovered automatically through dynamic metadata discovery) and apply any filters to create a new visualization of Claude Compliance data. Where possible, the complex queries generated by the filters and aggregations will be pushed down to Claude Compliance, 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.
10. Once you are finished configuring the dossier, click File -> Save.

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