Use the CData ODBC Driver for SAS Data Sets in MicroStrategy

MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData ODBC Driver for SAS Data Sets, you gain database-like access to live SAS Data Sets data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through creating a database instance for SAS Data Sets in MicroStrategy Developer and creating a Warehouse Catalog based on SAS Data Sets data.

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

Connect to SAS Data Sets as an ODBC Data Source

Information for connecting to SAS Data Sets follows, along with different instructions for configuring a DSN in Windows and Linux environments (the ODBC Driver for SAS Data Sets must be installed on the machine hosting the connected MicroStrategy Intelligence Server).

Set the following connection properties to connect to your SAS DataSet files:

Connecting to Local Files

• Set the Connection Type to "Local." Local files support SELECT, INSERT, and DELETE commands.
• Set the URI to a folder containing SAS files, e.g. C:\PATH\TO\FOLDER\.

Connecting to Cloud-Hosted SAS DataSet Files

While the driver is capable of pulling data from SAS DataSet files hosted on a variety of cloud data stores, INSERT, UPDATE, and DELETE are not supported outside of local files in this driver.

Set the Connection Type to the service hosting your SAS DataSet files. A unique prefix at the beginning of the URI connection property is used to identify the cloud data store and the remainder of the path is a relative path to the desired folder (one table per file) or single file (a single table). For more information, refer to the Getting Started section of 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.

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 SAS Data Sets 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 SASDataSets Sys]
Driver = CData ODBC Driver for SAS Data Sets
Description = My Description
URI = C:/myfolder

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

Create a SAS Data Sets Database Instance in MicroStrategy Developer

You can connect to SAS Data Sets in MicroStrategy Developer by adding a database instance based on the CData ODBC Driver for SAS Data Sets.^*

1. Open MicroStrategy Developer and select a Project Source.
2. Navigate to Administration -> Configuration Managers -> Database Instances and right-click to add a new instance.
3. Name the instance, select Generic DBMS as the database connection type, and create a new database connection.
4. In the database connection wizard, name the connection and create a new Database Login name, using filler values for the user and password. 👁 Create a new database login.
   
5. Select the DSN that you configured earlier as the ODBC data source (i.e., CData SASDataSets Sys). 👁 Choosing the DSN for the database connection.
   
6. Select the newly created database connection.
👁 The configured database instance.

7. In the Project Source, right-click the project and open the Project configuration.
8. Navigate to Database Instances and select the newly created database instance. 👁 Adding the new database instance to the project.
   
9. Close MicroStrategy Developer and restart the connected MicroStrategy Intelligence Server to complete the database instance creation.

With the database instance configured, you will now be able to connect to SAS Data Sets data from the Warehouse Catalog and Data Import.

Connect to SAS Data Sets Data from the Warehouse Catalog

Once you have created a database instance based on the ODBC Driver for SAS Data Sets, you can connect to data from the Warehouse Catalog.

1. Select your project and click Schema -> Warehouse Catalog. 👁 Creating the Warehouse Catalog
   
2. In the Read Settings for the Catalog, click Settings and set the queries to retrieve the schema:
   • To retrieve the list of tables, use the following query:

     SELECT 
      CatalogName NAME_SPACE,
      TableName TAB_NAME 
     FROM 
      SYS_TABLES
      

   • To retrieve the list of columns for selected tables, use the following query:

     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
      

   👁 Custom metadata queries.
   
3. Select tables to be used in the project. 👁 Selecting tables to be used in the project.
   

If you are interested in connecting to SAS Data Sets 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.