I built XML to replace an Analysis Services 2000 SP4 database using the
utility. I modified the XML and tried to alter the DSO Objects, but the
utility stopped with an error. Checking the treeview showed that only four
of the 10 or so cubes had been recreated. Then I tried to restore the
original database by running the original XML. Again the utility stopped
with an error. The log shows the following:

4/25/2006 11:21:14 AM: Write permissions for member security cannot be set
in cube role
4/25/2006 11:21:17 AM: Write permissions for member security cannot be set
in cube role
4/25/2006 11:21:18 AM: A dimension must have at least one enabled level.
4/25/2006 11:21:22 AM: Subscript out of range

I figure the earlier errors led to the later ones. I have been unable to
find any information on the "write permissions" error. Does anyone have an
idea? Everything was created through the AS GUI, so I don't understand why
the GUI did something that the DSO cannot.

I am ultimately just trying to change the cube's datasource (not just change
the connection parameters of the datasource itself). The reason is that I
have a development server and a production server, and I want to be able to
copy AS objects like cubes from one to the other. The datasource on both
servers has the same name, of course, because when you copy-paste a cube the
datasource is brought with it with the original name. However, I am using a
different connection string on the production server. This prevents me from
copying-pasting cubes from one server to the other because AS complains that
there is a datasource with the same name but a different connection string.
Since you can't just rename the datasource in the GUI, I resorted to this
utility to do it. Ideas??

Renaming the data source is fairly difficult, but it is doable using
the DSO. You literally copy out all of the dim & measure data from the
cube schema and reconstruct under the new database.

If you're unfamiliar with DSO structure MS Olap Scribe can give you a
pretty good introduction to how to access the various levels....
(We've developed a VBA tool for this but not sure I can post... not
personal work product. I'll check our regs.)

Easy solution long term is to just name the MSAS DB something generic
and just modify the connection strings. I wish some one would have
told me this before I ever build my first cube...

By now you've probably figured out how to do this. I just ran into all this
aggravation yesterday as we're moving our development cubs to production.
What we found is that you can change the datasource of a PARTITION in the
GUI. What we did was to change our development datasource to temporarily
point to production. We now had a datasource with the same name but so long
as it point to the same underlying DB as the one you're copying to then it's
ok.

After that it will complain if any of the shared dimensions used by the cube
you're copying have changed vs. the ones you're copying to. If so you'll have
to 1st delete them from the target. Afterwards, remember to bring that shared
dimension back into any cubes that were using it before.

This took awhile to figure out. I hope AS2005 makes it easier to move cubes
around.

Ken

"dustbort" wrote: