![]() |
VOOZH | about |
MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData ODBC Driver for Azure Data Catalog, you gain database-like access to live Azure Data Catalog data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through creating a database instance for Azure Data Catalog in MicroStrategy Developer and creating a Warehouse Catalog based on Azure Data Catalog data.
The CData ODBC driver offers unmatched performance for interacting with live Azure Data Catalog data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to Azure Data Catalog, the driver pushes supported SQL operations, like filters and aggregations, directly to Azure Data Catalog 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 Azure Data Catalog data using native MicroStrategy data types.
Information for connecting to Azure Data Catalog follows, along with different instructions for configuring a DSN in Windows and Linux environments (the ODBC Driver for Azure Data Catalog must be installed on the machine hosting the connected MicroStrategy Intelligence Server).
You can optionally set the following to read the different catalog data returned from Azure Data Catalog.
You must use OAuth to authenticate with Azure Data Catalog. OAuth requires the authenticating user to interact with Azure Data Catalog using the browser. For more information, refer to the OAuth section in 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 Azure Data Catalog 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 AzureDataCatalog Sys] Driver = CData ODBC Driver for Azure Data Catalog Description = My Description InitiateOAuth = GETANDREFRESH
For specific information on using these configuration files, please refer to the help documentation (installed and found online).
You can connect to Azure Data Catalog in MicroStrategy Developer by adding a database instance based on the CData ODBC Driver for Azure Data Catalog.*
With the database instance configured, you will now be able to connect to Azure Data Catalog data from the Warehouse Catalog and Data Import.
Once you have created a database instance based on the ODBC Driver for Azure Data Catalog, you can connect to data from the Warehouse Catalog.
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
If you are interested in connecting to Azure Data Catalog from other MicroStrategy products, you can read about connecting from MicroStrategy Web and connecting from MicroStrategy Desktop.
Note: connecting using a ODBC driver requires a 3- or 4-tier architecture.
Download a free trial of the Azure Data Catalog ODBC Driver to get started:
Download NowLearn more:
π Azure Data Catalog IconThe Azure Data Catalog ODBC Driver is a powerful tool that allows you to connect with live data from Azure Data Catalog, directly from any applications that support ODBC connectivity.
Access Azure Data Catalog data like you would a database - read, write, and update Azure Data Catalog Schemas, Tables, etc. through a standard ODBC Driver interface.