June 17, 2008 at 7:33 am
Does Cube migration wizard actual migrate the cube and render sql 2000 useless? or does it only make a copy of sql 2000 cube in sql 2005?
is there any other way to copy current sql 2000 cube into sql 2005?
thanks
June 17, 2008 at 7:53 am
I did not fully follow your question.
The SSAS migration does create a 2005 version of your 2000 AS database. The 2005 version will typically not process until you resolve some conflicts because the products are very different. Once the conflicts have all been resolved, you should be able to process the cube and browse it again.
I don't recommend "upgrading" cubes. The basic structure of Analysis Services changed significantly and what would be done to make an AS2000 cube perform well will not make an AS2005 cube perform well. In fact, the attribute relationships that are key to making your AS2005 cube perform well were not in AS2000. So, for a cube of any complexity it is usually best to create a new cube from scratch.
June 17, 2008 at 7:57 am
I think I am little confused about how this works.
If I was to rewrite the dts package that builds the cube I wouldnt be copying my current cube anyways to sql 2005. since my baseline tables are same I will have the same end result on sql 2005 given that the logic of sql 2005 ssis package is same as sql2000 dts package. Am I right?
or would I need to copy current cube to sql 2005 and then build on top of that?
thanks
June 17, 2008 at 8:01 am
I am not sure how you got from migrating a cube to the subject of DTS. Perhaps you have some of your terms wrong - I do not understand what you are trying to do.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply