Automating Analysis Services Deployment - 0 views

• 
  #1 Sergey Leifer on 07 Aug 10

   

  Automating build of Analysis Services Projects
  As you may be aware, an Analysis Services project consists of the following files:
  
  A project file (*.dwProj)
  One or more Data sources (*.ds)
  One or more Data source views (*.dsv)
  A database file (*.database)
  One or more cube files (*.cube) with their partition (*.partitions)
  One or more dimension files (*.dim)
  You can right click the project in Visual Studio and choose "build". What happens now seems to be a lot of called to DLL files executed by the integration between Visual Studio and the Analysis Services. The output of this build is the bin folder in your project directory. This folder contains a database file (*.asdatabase). The .asdatabase file is the one you want - you will see why later.
  
  Unlike other projects - which you can build using their proper compiler (Example: CSC.EXE, VBC.EXE) - Analysis Services does not seem to have a compiler executable.
  
  You could be tempted to run msbuild. Unlike most temptation this will result in disappointment - msbuild does not understand Analysis Services files.
  
  The only way I have found to automate the building of Analysis Services projects is to invoke Visual Studio from the command line. Say you have a project called: MyAsProject.dwProj. To build it and obtain the asdatabase file you execute the following:
  
  devenv MyAsProject.dwProj /rebuild Relase /project MyAsProject
  
  So far so good - now you have automated the createion of the .asdatabase file.
  
  You are not done yet. The asdatabase file provides the input to the Analysis Services Deployment Wizard. The spell cast by this wizard allows you to transform an asdatabase filen into an XML/A file. This XML/A file can be run on your deployment target - which will create the cube database.
  
  From the command line the Deployment Wizard can be run in two modes.
  
  The answer mode:
  Microsoft.AnalysisServices.Deployment.exe /a
  In this mode, you get to choose all the server specific settings and write them back to your bin directory. Check out the BOL documentation to find out exactly how this is implemented (You will find no defense for the naming of the executable in the documentation)
  
  Once you have your answers stored (which you will only do once) you want to automate the creation of the XML/A file. Execute:
  
  Microsoft.AnalysisServices.Deployment.exe MyAsProject.asdatabase /d /o:MyProject.xmla
  
  Voila! You have your xmla file, which you can copy to your deployment target and run. By the way. xmla files can be run from the command line using ascmd.exe

   

  <div class="cArrow"> </div><div class="cContentInner">Automating build of Analysis Services Projects <br /> As you may be aware, an Analysis Services project consists of the following files: <br /> <br /> A project file (*.dwProj) <br /> One or more Data sources (*.ds) <br /> One or more Data source views (*.dsv) <br /> A database file (*.database) <br /> One or more cube files (*.cube) with their partition (*.partitions) <br /> One or more dimension files (*.dim) <br /> You can right click the project in Visual Studio and choose "build". What happens now seems to be a lot of called to DLL files executed by the integration between Visual Studio and the Analysis Services. The output of this build is the bin folder in your project directory. This folder contains a database file (*.asdatabase). The .asdatabase file is the one you want - you will see why later. <br /> <br /> Unlike other projects - which you can build using their proper compiler (Example: CSC.EXE, VBC.EXE) - Analysis Services does not seem to have a compiler executable. <br /> <br /> You could be tempted to run msbuild. Unlike most temptation this will result in disappointment - msbuild does not understand Analysis Services files. <br /> <br /> The only way I have found to automate the building of Analysis Services projects is to invoke Visual Studio from the command line. Say you have a project called: MyAsProject.dwProj. To build it and obtain the asdatabase file you execute the following: <br /> <br /> devenv MyAsProject.dwProj /rebuild Relase /project MyAsProject <br /> <br /> So far so good - now you have automated the createion of the .asdatabase file. <br /> <br /> You are not done yet. The asdatabase file provides the input to the Analysis Services Deployment Wizard. The spell cast by this wizard allows you to transform an asdatabase filen into an XML/A file. This XML/A file can be run on your deployment target - which will create the cube database. <br /> <br /> From the command line the Deployment Wizard can be run in two modes. <br /> <br /> The answer mode: <br /> Microsoft.AnalysisServices.Deployment.exe /a <br /> In this mode, you get to choose all the server specific settings and write them back to your bin directory. Check out the BOL documentation to find out exactly how this is implemented (You will find no defense for the naming of the executable in the documentation) <br /> <br /> Once you have your answers stored (which you will only do once) you want to automate the creation of the XML/A file. Execute: <br /> <br /> Microsoft.AnalysisServices.Deployment.exe MyAsProject.asdatabase /d /o:MyProject.xmla <br /> <br /> Voila! You have your xmla file, which you can copy to your deployment target and run. By the way. xmla files can be run from the command line using ascmd.exe</div>

  ...

  Cancel

To Top