Ready to get started?

Download a free trial of the JSON Data Provider to get started:

 Download Now

Learn more:

JSON  Icon JSON ADO.NET Provider

Rapidly create and deploy powerful .NET applications that integrate with JSON web services.

Build an OLAP Cube in SSAS from JSON Services



Establish a connection to JSON services data from SQL Server Analysis Services, and use the JSON Data Provider to build OLAP cubes for use in analytics and reporting.

SQL Server Analysis Services (SSAS) serves as an analytical data engine employed in decision support and business analytics, offering high-level semantic data models for business reports and client applications like Power BI, Excel, Reporting Services reports, and various data visualization tools. When coupled with the CData ADO.NET Provider for JSON, you gain the capability to generate cubes from JSON services, facilitating more profound and efficient data analysis.

In this article, we will guide you through the process of developing and deploying a multi-dimensional model of JSON services by creating an Analysis Services project in Visual Studio. To proceed, ensure that you have an accessible SSAS instance and have installed the ADO.NET Provider.

Creating a Data Source for JSON

Start by creating a new Analysis Service Multidimensional and Data Mining Project in Visual Studio. Next, create a Data Source for JSON services in the project.

  1. In the Solution Explorer, right-click Data Source and select New Data Source.
  2. Opt to create a data source based on an existing or new connection and click New.
  3. In the Connection Manager, select CData ADO.NET Provider for JSON, enter the necessary connection properties, and click Next.

    See the Getting Started chapter in the data provider documentation to authenticate to your data source: The data provider models JSON APIs as bidirectional database tables and JSON files as read-only views (local files, files stored on popular cloud services, and FTP servers). The major authentication schemes are supported, including HTTP Basic, Digest, NTLM, OAuth, and FTP. See the Getting Started chapter in the data provider documentation for authentication guides.

    After setting the URI and providing any authentication values, set DataModel to more closely match the data representation to the structure of your data.

    The DataModel property is the controlling property over how your data is represented into tables and toggles the following basic configurations.

    • Document (default): Model a top-level, document view of your JSON data. The data provider returns nested elements as aggregates of data.
    • FlattenedDocuments: Implicitly join nested documents and their parents into a single table.
    • Relational: Return individual, related tables from hierarchical data. The tables contain a primary key and a foreign key that links to the parent document.

    See the Modeling JSON Data chapter for more information on configuring the relational representation. You will also find the sample data used in the following examples. The data includes entries for people, the cars they own, and various maintenance services performed on those cars.

    When you configure the connection, 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.

  4. Set the impersonation method to Inherit and click Next.
  5. Name the data source (CData JSON Source) and click Finish.

Creating a Data Source View

After you create the data source, create the data source view.

  1. In the Solution Explorer, right-click Data Source Views and select New Data Source View.
  2. Select the data source you just created (CData JSON Source) and click Next.
  3. Choose a foreign key match pattern that matches your underlying data source and click Next.
  4. Select JSON tables to add to the view and click Next.
  5. Name the view and click Finish

Based on the foreign key match scheme, relationships in the underlying data will be automatically detected. You can view (and edit) these relationships by double clicking Data Source View.

Note that adding a secondary data source to the Data Source View is not supported. When working with multiple data sources, SSAS requires both sources to support remote queries via OpenRowset which is unavailable in the ADO.NET Provider.

Creating a Cube for JSON

The last step before you can process the project and deploy JSON services to SSAS is creating the cubes.

  1. In the Solution Explorer, right-click Cubes and select New Cube
  2. Select "Use existing tables" and click Next.
  3. Select the tables that will be used for measure group tables and click Next.
  4. Select the measures you want to include in the cube and click Next.
  5. Select the dimensions to be created, based on the available tables, and click Next.
  6. Review all of your selections and click Finish.

Process the Project

With the data source, data source view, and cube created, you are ready to deploy the cube to SSAS. To configure the target server and database, right-click the project and select properties. Navigate to deployment and configure the Server and Database properties in the Target section.

After configuring the target server and database, right-click the project and select Process. You may need to build and deploy the project as a part of this step. Once the project is built and deployed, click Run in the Process Database wizard.

Now you have an OLAP cube for JSON services in your SSAS instance, ready to be analyzed, reported, and viewed. Get started with a free, 30-day trial of the CData ADO.NET Provider for JSON.