I've migrated 5 cubes from AS 2000 to 2005. I didn't get any errors during
this process nor do the logs indicate that there were any errors. I now have
2 functionally fine cubes and have problems with 3 of the cubes.

1. When I try to process one cube. An error says the select statement is
nested too deeply. This doesn’t make sense as this cube processed just fine
on the AS 2000 box. In looking more closely at the select statement in
question, it appears that some of my select statement has been truncated.

2. In processing another cube, I get an error that says an attribute key
cannot be found. I've tried to migrate this cube a second time and get the
same error.

3. The last problem is such that I can process the cube just fine and browse
it via SSMS, however I can't see it via excel or any other applcation.

If anyone out there has had problems with migrating cubes from 2000 to 2005
similar to mine. I'd appreciate any help.

AS2005 is more sensitive to metadata issues.
1. if your database as a column of 100chars and the key is defiend to store
50chars only, then AS don't process the cube.
take a close look at the errors to identify which attribute and column is in
default.

2. AS2005 execute optimized queries by default. AS2000 create some joins to
load data by default.
so in AS2000 this error may not appeared due to this join, the query simply
doesn't return the row in error, so AS2000 suffer no error.
but AS2005 don't do this join, so the row with the missing key is loaded
from the database and cause your issue.
you can log these rows in a file to do a manual cleansing or you can play
with the unknown members options (no AS2005 feature)
(you can also setup the cube to simply ignore these errors)

3. have you installed the 2005 drivers on the client station (the Excel
station)?
also use the surface area tool to verify that you authorize access to your
server.

Hope this will help you.


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