When I bring up BI Studio and select Open/Analysis Service Database, put in my server name (which is on the same machine that I'm running BI Studio), the click the "Database" drop down to select a database, it shows the following error in the bottom of the dialog:
Errors in the OLAP storage engine: The linked measure group with the ID of 'Sales', Name of 'Sales' cannot be processed because it contains MG dimension with the ID of 'Time', Name of 'Time' with different granularity attribute than its source object.
Errors in the metadata manager. An error occurred when loading the Sales measure group, from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\FoodMart.0.db\Trained Cube.0.cub\Sales.1.det.xml'.
Errors in the metadata manager. An error occurred when loading the Trained Cube cube, from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\FoodMart.0.db\Trained Cube.1.cub.xml'.
At this point, there doesn't seem to be any way to open any database in BI Studio. I always get that error, even if I try typing in another database name.
SQL Management Studio seems slightly better - I can at least connect there. But it only shows a couple of the databases that were on the machine - a bunch are missing. Any attempt to process or browse any of the databases results in the same error as above.
Any ideas?
Quoting the SP2 Readme: http://download.microsoft.com/download/2/B/5/2B5E5D37-9B17-423D-BC8F-B11ECD4195B4/ReadmeSQL2005SP2.htm
5.3.2 Analysis Services Databases that Contain a Linked Measure Group Might Become Unusable After Upgrade
Introduced in SQL Server 2005 SP2.
Analysis Services now requires that all dimensions contained in a linked measure group have the same granularity as the dimension in the source measure group. For example, if a time dimension in the source measure group has the day attribute as the granularity attribute, the linked measure group must also use the day attribute as the granularity attribute. The most common scenario for an Analysis Services database that violates this rule is a SQL Server 2000 Analysis Services database that was migrated by using a pre-release version of SQL Server 2005.
If you have a database that violates this granularity rule, you must modify the database containing the linked measure group before applying SP2. If you don't, the database will become invalid after SP2 is applied. Such invalid databases must be deleted.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Thanks Edward. RTFM, eh? Actually, I doubt it would have helped - this is a sample DB that I found somewhere, I wouldn't have realized it had this issue.
The problem is, I don't see a way to delete the database. The admin tools all barf with that error when I try to do anything, including deleting a DB. Is there some other way to nuke it?|||Unless you can go back to pre-SP2 build, you can stop the service, and manually delete all the files and folders in the Data directory. Then you will have to redeploy and reprocess the rest of your databases, unless you have backups in which case you would simply restore them.|||Thanks Mosha. I deleted the .0.db directory and the 0.db.xml file for the bad database (which I didn't need anyway, it was just for playing with), and have now regained access to my server. Any other files I should delete to clean things up?|||
This should be enough.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
I've recently installed SP2. All was fine initially but I'm now getting the error listed above having not changed anything significant (changed the membersname unique property of an attribute and then changed it back again). I'd been making changes all day to the attribute relationships and deploying without a problem.
I'm not using a linked measure group but the measure group it's reporting an error on has a different granularity key to the main measure group. Apart from changing the granularity key of the group that has a problem what can I do to fix this?
Mark
|||
I got the same error message which is posted in the first post here.
On a server which didn't had the foodmart database installed, I didn't get any problems after installing SP2. When I tossed the foodmart files away as described above, all problems vanished. It seems the problem here is the foodmart database. At the end of it Im glad I got my DB back, but "they" managed to scare the living daylight out of me with this, because I thought the whole AS had been turned into a wreck. Ironically the only database left in the management studio was the foodmart db. If you don't use it I would recommend to delete it before installing SP2.
Regards, Jeroen
No comments:
Post a Comment