Hi Steve,

We are currently using the following XMLA script:

<

Process xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">

<

Object

We do not use the Attribure Relationships because we have 2 hierarchies in the Time dimension.

If we do the members are messed up nad the behavior is different from what...

Hi,

The way we solve the problem in a specific cube was:

• Edit the cube in AS200, remove all dimension and add them again.
• Optimize schema and save the cube.
• Run the Migration Wizard...

Thanks Steve for you feedback.

We already use Parallel Process in AS2000, so using it in AS2005 would be a plus.

We are trying to create a IS package that creates a...

All of the registry changes are done on the 64-bit server.

The only link I have is http://support.microsoft.com/kb/916097, try contact your MS's contact person.

See also http://support.microsoft.com/kb/916097.

Hi,

We had the same problem and MS created a specific Hotfix. The problem is related with WOW (Windows-on-Windows) on the 64-bit. After installing W2K3 SP1 on the 32-bit server, it...

In AS2005 you can script a database or a cube to a xmla file. Right-click on the database (or cube) and select "Script Database as"...

I don't you create all partitions when developing the cube?

You just need to have a different view or named query for each partition.

As a Best Practice when possible I restrict...

Hi,

Being a 64-bit server it has “two registry” one regarding de 64-bits and the other for 32­bit. Relevant to AS2000 there are two relevant...

Hi all,

Thanks for your replies. However, it still does not solve the problem:

• The end users do not like Microsoft's add-in, they prefer the Pivot Tables.
• The "Group" does not allow to...

Hi,

From what I have read the Analysis Services can be installed in cluster in AS2005, but not in AS2000.

Hope it helps.

The way we do it is to have 2 (two) servers. One for processing/reconciling and the other for end-user querying. In AS2000 it means having 2 servers, however in SSAS...

Hi,

We have seen this problem in the past. In our case it was a priveledge problem.

I think we solved it by giving Full control to the "C:\Program Files" directory, given it...

You can either try the Metadata scripter included in the SQL Server 2000 Resource Kit, or simply archive/restore the database (this way you cannot rename the cube