Microsoft KB Archive/248659
Article ID: 248659
Article Last Modified on 2/24/2004
- Microsoft SQL Server OLAP Services
- Microsoft SQL Server 2000 Standard Edition
This article was previously published under Q248659
BUG #: 4737 (plato7x)
If you use the OLAP Manager add-in function to restore an OLAP database to a large repository (with a large number of objects) you may encounter performance or other problems. The speed of the restore process is highly dependent on the resources of the server you are using.
The restore may not complete if sufficient RAM is not available on the server.
The restore operation consumes a large amount of memory; possibly to the limit of memory on the server. If you use the Windows NT Performance Monitor to monitor the system resources, you see that the "Commit Bytes" counter under the "Memory" object is climbing rapidly. Eventually, this counter tops with the "Commit Limited" counter.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Microsoft tested this by using a Pentium II 450MHz computer with 256 MB of RAM and restored a Foodmart database to a repository with 2900+ entries in the Olapobject table. The restore did not complete. The Task Manager showed as "not responding" from the application and Windows NT started displaying a warning of running low in virtual memory message. Task Manager was used to end the application in this situation.
The size of the Msmdrep.mdb file in the preceding example is approximately 26 MB. Migrating the repository to SQL Server shows similar behavior. The performance of the restore process decreases sharply if the number of entries in the Olapobject table increases.
Additional query words: OLAP, Repository, Restore, Performance
Keywords: kbbug kbnofix KB248659