Deploy Model Solutions Using the Deployment Wizard
The Analysis Services Deployment Wizard uses the XML output files generated from a Microsoft SQL Server Analysis Services project as input files. These input files are easily modifiable to customize the deployment of an Analysis Services project. The generated deployment script can then either be immediately run or saved for later deployment.
You can deploy by using the wizard as discussed here. You can also automate deployment or use the Synchronize capability. If the deployed database is large, consider using partitions on target systems. You can also automate partition creation and population by using Analysis Management Objects (AMO).
Important
Neither the XML output files nor the deployment script will contain the user id or password if these are specified in either the connection string for a data source or for impersonation purposes. Since these are required for processing purposes in this scenario, you will add this information manually. If the deployment will not include processing, you can add this connection and impersonation information as needed after deployment. If the deployment will include processing, you can either add this information within the wizard or in the deployment script after it is saved.
In This Section
The following topics describe how to work with the Analysis Services Deployment Wizard, the input files, and the deployment script:
Topic |
Description |
|---|---|
Describes the various ways in which you can run the Analysis Services Deployment Wizard. |
|
Understanding the Input Files Used to Create the Deployment Script |
Describes which files the Analysis Services Deployment Wizard uses as input values, what each of those files contains, and provides links to topics that describe how to modify the values in each of the input files. |
Describes what the deployment script contains and how the script runs. |
See Also
Tasks
Synchronize Analysis Services Databases
Reference
Deploy Model Solutions with the Deployment Utility
Concepts
Deploy Model Solutions Using XMLA
Understanding the Input Files Used to Create the Deployment Script