This article was previously published under Q249698
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 3644 (SQLBUG_70)
With the initial release of the Addins for OLAP Services, the archive utility appears to work with files or archives larger than 2GB but causes the restore process to stop responding or fail when the archive is restored.
This is caused by a limitation with the CAB storage method, which cannot handle files larger than 2GB.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
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.