I'm building an OLAP database and including the resulting XMLA file in the installer for my product.
My project has aggregation designs on a couple of partitions - I can see these in the cube designer, I can edit them using BIDS Helper, but the resulting XMLA file is lacking any Aggregation Designs - it just contains an empty <AggregationDesigns /> element in each of the partitions where I've designed aggregations.
What am I missing to get the aggregation design to "stick"? The norm seems to be to deploy an aggregation design incrementally to an already deployed OLAP database, but that scenario doesn't work for me - I need to generate a complete XMLA script to create the database, including aggregation designs without deploying to SSAS.
Versions: SQL Data Tools 11 (SQL Server 2012, VS 2010), deploying to SQL Server 2008 R2.
Additional information:
- I can see my aggregation designs in the my-cube.partitions file
- I can see empty <AggregationDesign> elements in the my-cube.cube file
- I can see my aggregation designs in the my-database.asdatabase file
- I see no trace of aggregation designs whatsoever in the my-database.xmla file produced by running the deployment wizard.
- I'm generating the .XML file with m.a.d.exe {full-path-to-.asdatabase) /d /o:{full-path-to-.xmla)
- The .asdatabase, .configsettings, .deploymentoptions, .deploymenttargets files are all produced by building the Visual Studio project. I don't see anything in the project options to control deployment of aggregation designs.
- <DeploymentOptions><OptimizationSettingsDeployment> element contains Deploy
... and now, just as mysteriously, it's working. I think, maybe, that the problem was that I was using the deployment wizard from 2008 R2 on .asdatabase files produced by the 2012 tooling,and the wizard just silently fails without any error message, and
without replacing or erasing the existing .xmla file that was already there with no aggregation designs.
-cd Mark the best replies as answers!