Deployment Utility (Analysis Services - Multidimensional Data)
The Microsoft.AnalysisServices.Deployment utility lets you start the Microsoft SQL Server Analysis Services deployment engine from the command prompt. As input file, the utility uses the XML output files generated by building an Analysis Services project in Business Intelligence Development Studio. The 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.
The Microsoft.AnalysisServices.Deployment utility takes a set of files that provide the object definitions, deployment targets, deployment options, and configuration settings, and tries to deploy the object definitions to the specified deployment targets, using the specified deployment options and configuration settings. This utility can provide a user interface when invoked in answer file or output mode. For more information about how to use the user interface supplied for this utility to create answer files, see Using the Analysis Services Deployment Wizard.
The utility is located in the \Bin folder of the Analysis Services instance.
The utility can be run in the modes listed in the following table.
No user interface is displayed and all information needed for deployment is supplied by the input files. No progress is displayed by the utility in silent mode. Instead, an optional log file can be used to capture progress and error information for later review.
The Deployment Wizard user interface is displayed and user responses are saved to the specified input files for later deployment. Deployment does not occur in answer mode. The only purpose of answer mode is to capture user responses
No user interface is displayed and all information needed for deployment is supplied by the input files.
However, unlike silent mode, the output from the utility is written to an output script file, not sent to the deployment targets indicated in the input files. Unless the /d argument is specified, the utility connects with each deployment target to compare metadata while generating the output script file.
The following example shows how to deploy the Adventure Works DW sample Analysis Services project in silent mode, logging progress and error messages for later review:
<drive>:\Program Files\Microsoft SQL Server\100\Tools\Samples\AdventureWorks 2008R2 Analysis Services Project\bin
/s: C:\Program Files\Microsoft SQL Server\100\Tools\Samples\AdventureWorks 2008R2 Analysis Services Project\bin\deployment.log