![]() |
VOOZH | about |
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 SAS Data Sets, you gain the capability to generate cubes from SAS Data Sets 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 SAS Data Sets 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.
Start by creating a new Analysis Service Multidimensional and Data Mining Project in Visual Studio. Next, create a Data Source for SAS Data Sets data in the project.
Set the following connection properties to connect to your 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 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.)After you create the data source, create the data source view.
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.
π Discovered relationships in the data source view (Salesforce is shown).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.
The last step before you can process the project and deploy SAS Data Sets data to SSAS is creating the cubes.
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.
π Configuring the target server and database.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 SAS Data Sets 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 SAS Data Sets.
Download a free trial of the SAS Data Sets Data Provider to get started:
Download NowLearn more:
π SAS Data Sets IconRapidly create and deploy powerful .NET applications that integrate with SAS Data Sets.