On the production server, do you actually need the mdb / up-to-date file?

I think the msas service just runs off the registry key that points to the
directory of actual cube data...

?

You are correct. The actual runtime engine does not need the repository.
However any DSO application (and Analysis Manager) does. The problem with
getting the repository and the data folder out of sync is that you can
easily perform some kind of operation that overwrites the data folder
without getting a warning message or any notification. So our general advise
it is *ALWAYS* keep the two in-sync. For more information on this, see the
Analysis Services Operations Guide at:
http://www.microsoft.com/technet/pro.../anservog.mspx

--
Dave Wickert [MS]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Practices Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"PCH" <pch12 (AT) hotmail (DOT) com> wrote

The problem I have is each month I create a new cube + dimensions. I want
to automate the copying of the data files, but not bother with the database
since the production server is just queried through mdx oledb / adomd.

Perhaps I can script the archive option.. copy that..then script the
extracting of it.


"Dave Wickert [MSFT]" <dwickert (AT) online (DOT) microsoft.com> wrote

Look at using the DSO/XML tool.
http://www.microsoft.com/downloads/d...DisplayLang=en
After you script out and then back in the metadata (i.e. move the metadata
to the production server) all you need to do is process them on the
production server.
--
Dave Wickert [MS]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Practices Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"PCH" <pch12 (AT) hotmail (DOT) com> wrote