I have both limited hardware resources and the need to rebuild SQL 2005 OLAP cubes on the same server where they are being accessed. Because of the time needed to rebuild the cube it is preferable not to build it in place but, rather, to build it in another database and then backup/restore to the original location.
There doesn't appear to be a lot of documentation related to operating in this manner. The assumption appears to be that the cube structure will be deployed to another server or a backup is restored to its original location.
That works just fine except that when the underlying data structures (dimensions on which is it built) are changed it 'invalidates' both cubes. All of the objects (cube partitions and dimensions) are MOLAP which I thought made the entire cube structure 'stand alone'. If it is restored to a different physical server this problem does not occur.
Is it in some way considering the dimensions shared? Is there a setting or set of clean-up that needs to be done? Is there a different way to do this other than backup/restore?
Thanks in advance for any help that you could provide.
I am not very clear on what problems you mention you get after restoring the database on the same server under different name.
Try installing SP2 and see if that solves your problem.
Another approach is to install second instance of Analysis Server on the same machine and use it for processing only. This should both save you the hardware and provide level of separation you are trying to achieve.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
No comments:
Post a Comment