Showing posts with label migration. Show all posts
Showing posts with label migration. Show all posts

Sunday, March 11, 2012

Cubes Migration problem

Hello,
I have 3 cubes with 3 shared dimensions (dates, ids, factors) in SQL Server 2000 environment. After the cubes migration to SSAS 2005
using Analysis Services Migration Wizard I got individual dimensions for
each cube : dates, dates1, dates2, ids,ids1, ids2, factors, factors1,
factors2. This makes the problem for my cubes MDX queries and based on it applications.
The question is how to preserve shared dimensions during cubes migration? And another qustion: is it possible to have in the database dimensions with the same name

(like dates and dates)?

Thanks,
GB

Migration is not going to create a best possible stucture for your cube. It operates in generic manner trying to cover all possible cube designs.

After you've migrated you need to go over your cube design and improve it. You should try to re-structure your cubes so you have a single version of database dimension ( you probably dont neet dates1, dates2, ids1, ids2 ...).

You should also take a look if possible to create a single cube with several measure groups. Looks like this might be the case. If you have multiple dimensions shared between several cubes, chances you can model the situation by creating multiple measure groups.

Take a look at sample Adventure Works project, see the stucture of Adventure Works cube. This should give you clues for having better cube design.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Thursday, March 8, 2012

Cubes Migration problem

Hello,
I have 3 cubes with 3 shared dimensions (dates, ids, factors) in SQL Server 2000 environment. After the cubes migration to SSAS 2005
using Analysis Services Migration Wizard I got individual dimensions for
each cube : dates, dates1, dates2, ids,ids1, ids2, factors, factors1,
factors2. This makes the problem for my cubes MDX queries and based on it applications.
The question is how to preserve shared dimensions during cubes migration? And another qustion: is it possible to have in the database dimensions with the same name

(like dates and dates)?

Thanks,
GB

Migration is not going to create a best possible stucture for your cube. It operates in generic manner trying to cover all possible cube designs.

After you've migrated you need to go over your cube design and improve it. You should try to re-structure your cubes so you have a single version of database dimension ( you probably dont neet dates1, dates2, ids1, ids2 ...).

You should also take a look if possible to create a single cube with several measure groups. Looks like this might be the case. If you have multiple dimensions shared between several cubes, chances you can model the situation by creating multiple measure groups.

Take a look at sample Adventure Works project, see the stucture of Adventure Works cube. This should give you clues for having better cube design.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Saturday, February 25, 2012

Cube migration from AS2000 to AS2005

I have problem migrating the cube from AS2000 to AS2005. I am using the migrationwizard.exe to migrate the cube.

I have entered the SQL Server 2000 Analysis services source server and SQL 2005 AS destination server. When i click enter i get this message:

Source server: The 'MSOLAP.2' provider is not registered on the local machine.

I am unable to proceed further. I would appreciate if someone can help me.

Thanks.

You are not able to connect to AS 2000. Try if you can access 2000 version of cube from the same machine in which you are running migrationwizard.|||

Thanks for your reply.

Do you mean connecting AS2000 cube from SQL 2005 management studio? I have tried this and I get the message

No connection could be made because the target machine actively refused it (system).

I have no problem connecting AS2000 cubes on Analysis Manager.

Please let me know how to resolve this. Thanks again.

|||

Not very sure It may have to do with MSOLAP version. Check

MSOLAP80.DLL or MSOLAP90.DLL must exist in C:\Program Files\Common Files\System\Ole DB directory. Check if its in system path.

|||Yes. Both MSOLAP80.Dll and MSOLAP90.Dll exists on the Ole DB directory.|||Just another guess MSOLAP80.Dll file might be bad. Try reinstall or copy from other machine.|||Dear Gopal!

Have you succeeded in the AS2000 to AS2005 migration? I'm suffering from the same problem you described and don't know what to do next.

Do you have a solution?
Thanks in advance
|||

SQL Management Studio 2005 will indeed not connect to AS2000. You will need to use Analysis Manager for that (do you have it on the machine where you run Migration Wizard ?)

The error message indicates you have a faulty install for DSO or one of it's components (Migration Wizard uses DSO to connect to the AS2000 server, to read the meta-data and transfer it to the AS2005 server). Try to re-install DSO and the msolap provider from AS2000.

On the machine running the Migration Wizard, what is the file version for msmddo80.dll (in "%ProgramFiles%\Common Files\Microsoft Shared\DSO") ?

If re-installing DSO from AS2000 doesn't work or doesn't fix the problem, re-run the SQL 2005 Setup and install the 'Backward Compatibility' components (that will install DSO version 8.5).

Cube migration from AS2000 to AS2005

I have problem migrating the cube from AS2000 to AS2005. I am using the migrationwizard.exe to migrate the cube.

I have entered the SQL Server 2000 Analysis services source server and SQL 2005 AS destination server. When i click enter i get this message:

Source server: The 'MSOLAP.2' provider is not registered on the local machine.

I am unable to proceed further. I would appreciate if someone can help me.

Thanks.

You are not able to connect to AS 2000. Try if you can access 2000 version of cube from the same machine in which you are running migrationwizard.|||

Thanks for your reply.

Do you mean connecting AS2000 cube from SQL 2005 management studio? I have tried this and I get the message

No connection could be made because the target machine actively refused it (system).

I have no problem connecting AS2000 cubes on Analysis Manager.

Please let me know how to resolve this. Thanks again.

|||

Not very sure It may have to do with MSOLAP version. Check

MSOLAP80.DLL or MSOLAP90.DLL must exist in C:\Program Files\Common Files\System\Ole DB directory. Check if its in system path.

|||Yes. Both MSOLAP80.Dll and MSOLAP90.Dll exists on the Ole DB directory.|||Just another guess MSOLAP80.Dll file might be bad. Try reinstall or copy from other machine.|||Dear Gopal!

Have you succeeded in the AS2000 to AS2005 migration? I'm suffering from the same problem you described and don't know what to do next.

Do you have a solution?
Thanks in advance
|||

SQL Management Studio 2005 will indeed not connect to AS2000. You will need to use Analysis Manager for that (do you have it on the machine where you run Migration Wizard ?)

The error message indicates you have a faulty install for DSO or one of it's components (Migration Wizard uses DSO to connect to the AS2000 server, to read the meta-data and transfer it to the AS2005 server). Try to re-install DSO and the msolap provider from AS2000.

On the machine running the Migration Wizard, what is the file version for msmddo80.dll (in "%ProgramFiles%\Common Files\Microsoft Shared\DSO") ?

If re-installing DSO from AS2000 doesn't work or doesn't fix the problem, re-run the SQL 2005 Setup and install the 'Backward Compatibility' components (that will install DSO version 8.5).