Hi all,
I have a big Olap cube (no partitions) runing on SQL2000 standard
edition,
that recenly began to fail on archiving
giving the following error:
"One of the data files is too large to be stored inside a CAB file. "

According to this KB:
http://support.microsoft.com/default...;en-us;Q303415

MS confirmed it to be a bug but the fix is for SQL7 not for SQL2000:
http://support.microsoft.com/kb/249698/EN-US/

Is there also a fix for SQL 2000 ?

The 2Gb limit is a limit in the .CAB file format. Unfortunately all the
"Fix" for SQL 7.0 does is to check the file sizes before it attempts to
archive them so that it can fail earlier.

The following is taken from the last 2 paragraphs of the last link you
referred to, the last paragraph tells you the work around if you have
individual files larger than 2Gb.

<snip>
The OLAP Services Addins that ship with Service Pack 2 contain an
enhanced archive utility that checks the total size of the database
archive and creates multiple files if the CAB size will exceed 2GB. The
utility also checks the size of each individual database file (data,
map, index, and so forth) that will be archived and will not attempt to
archive a database if any of the individual files is larger than 2GB.

In situations in which a large data file prevents use of the archive
utility for backing up OLAP Services databases, another backup utility,
such as Windows NT Backup, should be used to make backups of all files
in the OLAP Services Data folder. If the OLAP Services Repository is
stored in Microsoft Access, then the Msmdrep.mdb file located in the
\OLAP Services\Bin folder should also be included in the backup. If the
repository has been moved to Microsoft SQL Server using the Repository
Migration Wizard, then the OLAP repository database should be included
in the backup plan for SQL Server.
<snip>

HTH

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <1132472967.821046.151680 (AT) g47g2000cwa (DOT) googlegroups.com>,
yaniv.inbar (AT) retalix (DOT) com says...

AS Operations Guide discusses this extensively.
The restriction is that anyone file must not exceed 2GB (as Darren says,
this is a limit of the CAB file technology). If you start to exceed this
limit, you have two options:
1) use partitioning to reduce the size of the files down below 2GB
2) switch to using file-level backup/restore -- discussed extensively in the
Guide
http://www.microsoft.com/technet/pro.../anservog.mspx
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Darren Gosbell" <jam (AT) newsgroups (DOT) nospam> wrote

You can use my utility
http://www.activeinterface.com/b2005_03_15.html
Chris
"yaniv" <yaniv.inbar (AT) retalix (DOT) com> wrote