Use the CData JDBC Driver for Vercel in MicroStrategy
MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData JDBC Driver for Vercel, you gain database-like access to live Vercel data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through creating a database instance for Vercel in MicroStrategy Developer and create a Warehouse Catalog for the Vercel data.
The CData JDBC Driver offers unmatched performance for interacting with live Vercel data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to Vercel, the driver pushes supported SQL operations, like filters and aggregations, directly to Vercel 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 Vercel data using native MicroStrategy data types.
Connect to Vercel in MicroStrategy Developer
You can connect to Vercel in MicroStrategy Developer by adding a database instance based on the CData JDBC Driver for Vercel.* Before you begin, you will need to install the JDBC Driver for Vercel on the machine hosting the MicroStrategy Intelligence Server that your instance of MicroStrategy Developer is connected to.
- Open MicroStrategy Developer and select a Project Source.
- Navigate to Administration -> Configuration Managers -> Database Instances and right-click to add a new instance.

- Name the instance, select Generic DBMS as the database connection type, and create a new database connection.

- In the database connection wizard, name the connection and create a new Database Login name, setting the user and password for Vercel.

- On the Advanced tab for the connection wizard, set the additional connection string parameters as follows.
- Add the JDBC keyword to the connection string.
- Set MSTR_JDBC_JAR_FOLDER to the path of the directory containing the JAR file for the JDBC driver. (C:\Program Files\CData JDBC Driver for Vercel\lib\ on Windows.)
- Set DRIVER to cdata.jdbc.api.APIDriver, the driver class.
- Set URL to the JDBC URL for the Vercel driver, which contains the necessary connection properties.
Using API Key Authentication
Vercel uses Bearer token authentication. You can use either a personal access token or an OAuth access token as the API key.
To obtain a personal access token:
- Log into your Vercel account at https://vercel.com/
- Navigate to Account Settings > Tokens.
- Click Create Token, enter a name and expiration, and click Create.
- Copy the generated token (it will only be shown once).
After obtaining your token, set the following connection properties:
- AuthScheme: Set this to APIKey.
- APIKey: Set this to your Vercel personal access token or OAuth access token.
Example Connection String
Profile=C:\profiles\Vercel.apip;AuthScheme=APIKey;APIKey=your_access_token;
Working with Teams
Many Vercel resources are scoped to a team. To scope all requests to a specific team, set the TeamId connection property to your team's ID. You can find your team ID by querying the Teams table or from the Vercel dashboard. Alternatively, you can specify TeamId in your SQL queries using the WHERE clause where supported.
Connecting to Vercel
Once the authentication is configured, you can connect to Vercel and query data from any of the available tables such as Projects, Deployments, Teams, and Domains.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Vercel JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.api.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.
Typical additional connection string properties follow:
JDBC;MSTR_JDBC_JAR_FOLDER=PATH\TO\JAR\;DRIVER=cdata.jdbc.api.APIDriver;URL={jdbc:api:Profile=C:\profiles\Vercel.apip;AuthScheme=APIKey;APIKey=your_access_token;};
- Ensure that you have not selected an ODBC data source (this will trigger MicroStrategy to use the additional connection string parameters to build the database instance) and click OK.
- Click OK to close the database instance wizard.
- In the Project Source, right-click the project and open the Project configuration.
- Navigate to Database Instances, select the newly created database instance, and click OK.
- 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 Vercel data from the Warehouse Catalog and Data Import.
Connect to Vercel Data from the Warehouse Catalog
Once you have created a database instance based on the JDBC Driver for Vercel, you can connect to data from the Warehouse Catalog.
- Select your project and click Schema -> Warehouse Catalog.

- 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 * 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
- To retrieve the list of tables, use the following query:
- Select tables to be used in the project.

Using the CData JDBC Driver for Vercel in MicroStrategy, you can easily create robust visualizations and reports on Vercel data. Read our other articles on connecting to Vercel in MictroStrategy Web and connecting to Vercel in MicroStrategy Desktop for more information.
Note: Connecting using a JDBC Driver requires a 3- or 4-Tier Architecture.