Hi All,

I have a script that uses VBScript and DSO to delete and add dimensions to
cubes and reprocess them. We restore an archive of the database first.

We're trying to get our product to work with SQL Server 2005. I found that
I had to copy the msmdrep.mdb file from the 2000 installation and point the
DSO config settings (e.g., DSO/RemoteRepositoryConnectionString) to it. I
finally was able to see the "old" olap databases in SQL Management Studio.

The VBScript is failing with the following error:
Error Description: My OLAP Server;DSS;ServiceUtilization: Cannot parse the
JoinClause.

When I try to process the "old" cubes manually in SQL Management Studio,
they seem to process, but when I try to browse the data, I get the following
error:
TITLE: Microsoft SQL Server Management Studio
------------------------------

The '<ObjectUrn>
<Cube>ServiceUtilization</Cube>
</ObjectUrn>' object cannot be found. (Microsoft.DataWarehouse.VsIntegration)

Does anyone know if the DSO backward compatibility in 2005 is meant to
handle shared dimension and cube *updates*. Is the archive restore the
problem? We're aware of the new 2005 APIs, but we need to get our product
working with 2005 with the minimum of code changes :-)

Thanks in advance for any help!

DSO is no longer supported in AS2005

there is a set of new XML/A commands to access/manage your server/cubes.
for example, to process a cube, right click on it in the management studio,
click process and in the popup windows you'll found a new button "Script"
which generate the script for you...

but you can write the script yourself.

search in the BOL for more information.

"Dand" <Dand (AT) discussions (DOT) microsoft.com> wrote

Just to clarify. A form of DSO (DSO9) is still supported for migrated
databases. However, the recommended method is to switch to use the new .NET
object model called AMO which will give you access to the new features in AS
2005. Once you use the new Tools to modify a migrated database you will no
longer be able to use DSO9 against it.

You can also use XMLA commands to access/manage your cubes but if you want
to use an object model then AMO is the recommended option.

Thanks,
Akshai

--
--
This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Jéjé" <willgart_A_ (AT) hotmail_A_ (DOT) com> wrote

"Akshai Mirchandani [MS]" wrote:

Thank you for the replies. However, the question is why my scripts aren't
running. Microsoft has provided a DSO backward compatibility layer.
Therefore, my scripts should work. If not, I need to know what functionality
is not available. I understand that it is recommended to use the new APIs,
but that's not my goal.

Our customers cannot easily buy SQL Server 2000, so we need to go to 2005.
Does Microsoft really expect us to rewrite our scripts?

"Akshai Mirchandani [MS]" wrote:

I've rewritten mine and had the same reservations you had at first.

It's taken a few weeks, however it was WELL worth it. Can't say that enough.


"Dand" <Dand (AT) discussions (DOT) microsoft.com> wrote

The DSO backward compatibility layer only works when the database objects
are migrated/upgraded from AS 2000. As soon as you use the new Tools to
manipulate/alter the objects, the DSO programs will not work.

Additionally, you will not be able to use the new
properties/collections/objects that are available in the new UDM model
(measure groups, perspectives, etc.).

Unfortunately, this means that yes -- you would need to rewrite scripts if
you want them to work against new AS 2005 cubes. There has been so much
change in the model that it is very difficult to map the new concepts into
the older object model...

It would be helpful if you can be more specific about what error/failure you
see with your scripts. Perhaps it is an unrelated issue.

Thanks,
Akshai
--
This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Jesse O" <jesperzz (AT) hotmail (DOT) com> wrote