Build an OLAP Cube in SSAS from AlloyDB Data

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 AlloyDB, you gain the capability to generate cubes from AlloyDB data, 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 AlloyDB data 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 AlloyDB

Start by creating a new Analysis Service Multidimensional and Data Mining Project in Visual Studio. Next, create a Data Source for AlloyDB data 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 AlloyDB, enter the necessary connection properties, and click Next.

   The following connection properties are usually required in order to connect to AlloyDB.

   • Server: The host name or IP of the server hosting the AlloyDB database.
   • User: The user which will be used to authenticate with the AlloyDB server.
   • Password: The password which will be used to authenticate with the AlloyDB server.

   You can also optionally set the following:

   • Database: The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
   • Port: The port of the server hosting the AlloyDB database. This property is set to 5432 by default.

   Authenticating with Standard Authentication

   Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.

   No further action is required to leverage Standard Authentication to connect.

   Authenticating with pg_hba.conf Auth Schemes

   There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.

   Find instructions about authentication setup on the AlloyDB Server here.

   Authenticating with MD5 Authentication

   This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.

   Authenticating with SASL Authentication

   This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.

   Authenticating with Kerberos

   The authentication with Kerberos is initiated by AlloyDB Server when the ∏ is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos.

   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.

   👁 Setting the Connection properties (Salesforce is shown.)
   
4. Set the impersonation method to Inherit and click Next. 👁 Setting the impersonation method.
   
5. Name the data source (CData AlloyDB 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 AlloyDB Source) and click Next.
3. Choose a foreign key match pattern that matches your underlying data source and click Next. 👁 Selecting the Foreign key match pattern.
   
4. Select AlloyDB tables to add to the view and click Next. 👁 Selecting Tables (Salesforce is shown).
   
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 AlloyDB

The last step before you can process the project and deploy AlloyDB data 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. 👁 Selecting measure group tables (Salesforce is shown).
   
4. Select the measures you want to include in the cube and click Next. 👁 Selecting measures (Salesforce is shown).
   
5. Select the dimensions to be created, based on the available tables, and click Next. 👁 Selecting dimensions (Salesforce is shown).
   
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 AlloyDB data 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 AlloyDB.