Adam Bean (8/10/2012)
Hey all,Sadly, I know close to nothing about SSAS. I recently joined a new company and we're working on some environment architecture. They're currently targeting the utilization of a "stage" environment to perform all of our SSIS/SSAS work on to stage the data appropriately to be QA'd by users and keep the load off the production environment. From there, they want to be able to migrate the data (easy on the database end) as well as the appropriate SSAS pieces.
Now, I see within SSAS you have the ability to perform a sync. With that though, a few questions:
- Does this bring both the database and the cube(s)?
-- If it doesn't bring the cube(s), how do you handle that?
- The XML it can generate, how would you run that outside of SSMS (to say have it launched from within an app)
Again, I'm a complete SSAS noob sitting here reading/playing trying to get up to speed very fast. Any and all ideas/thoughts/recommendations around this matter would be very much so appreciated.
Thanks!
I'll answer what I can:
synching - we use this as it sounds you intend to - process in one place, synch to production. This brings the cube only. once the cube is processed, you can consider the data to already be "in it".
I only use the XMLA scripts if I have made a cube structure change in development to alter the cube in staging. not clear on what you are attempting to use XML to launch???