I recently defined deployment of SSAS tabular model for one of the projects I am working on. Here it goes.
As development team won’t have any access to other environments like Test or PROD, all the deployable will be handed over to DBA team who can then make the deployment with the procedure described below.
For the sake of simplicity, the deployment folder is named as SSASDeploymentFolder here. This is symbolic and in real case it would be somewhere in the shared drive and will be accessible by both DBA and development team.
The development team will generate all the deployment files required to make the deployment. This can be done by accessing the TFS and opening tabular project in SSDT and then build the project. After successful build all the files will be available in the bin folder of the project.
Right click on the project opened in SSDT and then click Build. Following screenshot illustrates how to build the project:
After successful build you will find the required files in the bin folder as below:
Development team will copy these files below to the SSASDeploymentFolder and inform the DBA team with necessary process flow.
Note: The name Model is default name. This can be replaced with the project name. But it is important that all three files need to have same name with corresponding extensions and need to be placed at same folder.
Microsoft Ships a deployment wizard to deploy SSAS tabular model. This can be found in the following folder (in a 32-bit system):
C:\Program Files\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Microsoft.AnalysisServices.Deployment.exe
This wizard takes input file and makes the deployment in the target environment with necessary configuration options as illustrated below.
Start the wizard
You can double click above mentioned exe file or start it through start menu. It can be found under Microsoft SQL Server 2012 > Analysis Services > Deployment Wizard
Choose the input file copied to the deployment folder: Model.asdatabase
Specify the target (SSAS Tabular server) where the deployment will be made. Also specify the name of the AS database. Note that name of the database may or may not same as the name of the tabular model. The name of the model (cube) has been specified while development in SSDT.
Specify the deployment for partitions and roles. Choose the options as in the screenshot below:
Specify the Configuration options for the tabular model (cube).
You need to change the connection string for the data source of the cube. In this case it is the data warehouse. Also specify the account using which it will connect to the data source. The screenshot illustrates.
Select full processing option.
Final Step in wizard. DO NOT tick for the create deployment script.
If you tick, it would only generate a xml file scripting all the tabular model with the deployment options. This file can later be executed through management studio to make the deployment.
The deployment will run for a while – It depends on how much data is processing from the source. After it completes click Next and then Finish.
Verify using Management studio that your deployment is successful and as expected.
In your case you may need to change some or all the configuration options. Let me know your thoughts…