Use the CData ODBC Driver for Linear in MicroStrategy Web
MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData ODBC Driver for Linear, you gain database-like access to live Linear data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through adding Linear as external data in MicroStrategy Web and creating a simple visualization of Linear data.
The CData ODBC driver offers unmatched performance for interacting with live Linear data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to Linear, the driver pushes supported SQL operations, like filters and aggregations, directly to Linear 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 Linear data using native MicroStrategy data types.
Connect to Linear as an ODBC Data Source
Information for connecting to Linear follows, along with different instructions for configuring a DSN in Windows and Linux environments (the ODBC Driver for Linear must be installed on the machine hosting the connected MicroStrategy Intelligence Server).
You can authenticate to Linear with a personal API key or with OAuth 2.0. The API key is the simplest option for connecting with your own Linear account.
Authenticating with an API Key
Set the following connection properties:
- AuthScheme: Set this to APIKey.
- APIKey: A Linear personal API key.
To create a personal API key, log in to Linear, open Settings > Security & access > Personal API keys, select New API key, and create it. Copy the key immediately, because Linear shows it only once.
Authenticating with OAuth
OAuth requires a custom OAuth application registered in Linear (Settings > API > OAuth applications), which provides the OAuthClientId and OAuthClientSecret. Two flows are supported:
- Authorization code: Set AuthScheme to OAuth, InitiateOAuth to GETANDREFRESH, and provide OAuthClientId, OAuthClientSecret, and the CallbackURL defined in your application (e.g., http://localhost:33333). The driver opens Linear in your browser so you can grant access.
- Client credentials: Set AuthScheme to OAuthClient and provide OAuthClientId and OAuthClientSecret. This authenticates the application itself, with no browser interaction, and suits machine-to-machine integrations.
By default, the driver requests the read,write scopes. The driver refreshes the access token automatically when it expires.
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 Linear 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 Linear Sys]
Driver = CData ODBC Driver for Linear
Description = My Description
AuthScheme = APIKey
APIKey = myAPIKey
For specific information on using these configuration files, please refer to the help documentation (installed and found online).
Connect to and Visualize Linear Data using MicroStrategy Web
Once you have created a database instance in MicroStrategy Developer and connected it to a project, you can perform a data import of Linear data from MicroStrategy Web. Alternatively, you can create a new data source based on the ODBC Driver.*
- Open MicroStrategy Web and select your project.
- Click Add External Data, select Databases, and choose Select a Table as the Import Option.
- In the Import from Tables wizard, click to add a new data source.
- Select DSN Data Sources
- Set the DSN property to the previously configured DSN (CData Linear Sys)
- Set the Version property to Generic DBMS
- Set the User and Password properties (or use filler values)
- Set the Data Source Name
- After creating the data source, click to edit the catalog options and set the following queries and click OK.
- SQL statement to retrieve tables available in the data source
SELECT CatalogName NAME_SPACE, TableName TAB_NAME FROM SYS_TABLES - SQL statement to retrieve columns for the selected 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
- SQL statement to retrieve tables available in the data source
- Drag a table into the pane.
Note: Since we create a live connection, we can import whole tables and utilize the filtering and aggregation features native to the MicroStrategy products. - Click Finish, choose to the option to connect live, save the query, and choose the option to create a new dossier.

- Choose a visualization, choose fields to display, and apply any filters to create a new visualization of Linear 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 Linear, 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.

- Once you have finished configuring the dossier, click File -> Save.
Using the CData ODBC Driver for Linear in MicroStrategy Web, you can easily create robust visualizations and reports on Linear data. Read our other articles on connecting to Linear in MicroStrategy and connecting to Linear in MicroStrategy Desktop for more examples.
Note: connecting using a ODBC driver requires a 3- or 4-tier architecture.