Deployment tools for SSAS Tabular Cube Models
This extension adds four tasks to Azure DevOps which are ideal for integrating tabular cube models into your CI pipeline. With these tasks you can deploy, update, process and drop tabular cube models on an on-premise Microsoft SQL Server Analysis Services (SSAS) server.
As part of your CI pipeline you can use these tasks to deploy and populate your cube with data so you can run a suite of automated tests against your cube.
These tasks can also be used to automate the deployment of tabular cubes using Release pipelines in Azure Pipelines in a continuously delivery scenario. For those using Octopus Deploy or Chef, you can use the underlying PowerShell module DeployCube to perform the same deployment tasks.
The screenshots below show how the components can be used in your CI pipeline.
First the pipeline builds the solution using MsBuild. The solution contains a SQL Server database project and a SSAS tabular cube project, so the build produces a DACPAC for the SQL database and an .asdatabase file for the tabular cube model. Next, we deploy the SQL Database using our sister component Publish DACPAC using a DAC Publish Profile
We ensure the build server has no remnants of the previous build by dropping the tabular model if it exists using the Drop SSAS tabular cube model task. We use the Deploy SSAS Tabular Cube Model task to publish the tabular cube to the build server. We then update the connection string inside the cube so that it points to the previously deployed SQL Server database using the Update SSAS tabular cube data source task. Next, we process the cube so that it contains data using the Process SSAS Tabular cube model task. The cube would now be ready for you to run a suite of automated tests.
Deploy SSAS Tabular Cube Model
When you perform a build in a Visual Studio cube project, it creates an .asdatabase file which defines the entire model including dimensions, attributes, measures, data sources and DAX calculations. In the above pipeline MsBuild to create the .asdatabase file from the Visual Studio solution.
Pre-requisites for Deploy SSAS Tabular Cube Model task
The following pre-requisites need to be installed on your in-house build agent for the Deploy SSAS Tabular Cube Model task to work properly.
The basic inputs for the Deploy SSAS Tabular Cube Model task are simply the path to the .asdatabase file, the target SSAS server and target cube database name. Note that the tabular cube is always deployed without processing, as the data source connection settings are likely to be incorrect. The Process SSAS Tabular cube model task can be used to load data into the cube.
The task also offers the following deployment options for fine control over your deployment.
Update SSAS tabular cube data source
The Update SSAS tabular cube data source task allows you to change the connection string to the underlying data source. The task reads the existing connection string and replaces the server name and database name to those supplied in the task. Note that this task works on the deployed tabular cube, so must be done post-deployment.
Process SSAS Tabular cube model
The Process SSAS Tabular cube model task allows you to process the newly deployed tabular cube model so that it contains data. Once the cube contains data, you can run a suite of automated tests against your cube to check it contains the right values.
Drop SSAS tabular cube model
The Drop SSAS tabular cube model task is usually used at the beginning of your build pipeline to ensure the target server has no remnants of previous builds.
MsBuild is used to build the Visual Studio solution that contains a SQL Server database project and the SSAS tabular cube project. This produces a DACPAC for the SQL database and an .asdatabase file for the tabular cube model.
Publish DACPAC using a DAC Publish Profile Task
We deploy the SQL Database using our sister component Publish DACPAC using a DAC Publish Profile with the following settings: