5.5GB cube is too large to be stored in a .CAB

  • Hi all, how can a Cube be backed up that has a size of 5.5GB on SQL-Server 2000 SP3a Analysis Services? Ralf.

  • Yikes! 5GB! Well, if you can't figure out how to make it smaller...

    What about storing it in ROLAP mode instead of MOLAP? That way you can use SQL backup/restore on the data.

  • All the archive utility does is to copy the data files into a .cab file.  We have the same issue and instead of using the archive utiltity we just schedule an xcopy job.  Make sure you include the repository in your backup plans though.

    We use this method to restore to two different AS servers that are load balanced and do all the processing on a third server, it works fine.

    /*****************

    If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek

    *****************/

  • i've run into this same situation and to resolve the problem, we've partitioned the cube so that each partition is below the 2GB limit for the msmdarch utility.  this may be an option, otherwise you'll need to use some other file-based utility to perform backups.

  • hi chris, that was the korrekt reason. after dividing the cube into 4 partitions the backup to a .cab-file works. many thanks! ralf

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply