How to maintain a Microsoft Content Management Server database (836646)
The information in this article applies to:
- Microsoft Content Management Server 2001
- Microsoft Content Management Server 2001 SP1
- Microsoft Content Management Server 2001 SRP2
- Microsoft Content Management Server 2002
- Microsoft Content Management Server 2002 SP1
- Microsoft Content Management Server 2002 SP1a
SUMMARYThis article discusses general best practices for maintaining your Microsoft Content Management Server (MCMS) database by using tools that are included with the MCMS client tools and with SQL Enterprise Manager.
This article also discusses a substitute process for the Background Process (BP). This substitute process includes a SQL stored procedure version of the BP together with an ASP sample script to delete expired postings and to delete expired pages in your MCMS database.
Note The substitute process is for MCMS 2001 only. INTRODUCTIONIf you update your production Microsoft Content Management Server (MCMS) database frequently by using the Site Deployment process, you may notice that your production database is significantly larger than either your development database or your authoring database.
The difference in the database size occurs because the Site Deployment process creates an archive version of the object that it replaces during an Import process. However, the Background Process (BP) does not automatically delete these archive versions because these archive versions are not expired items or orphan objects in the database.REFERENCES
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
813513
CMS server generates 404 and 500 errors during background processing
Modification Type: | Minor | Last Reviewed: | 8/19/2005 |
---|
Keywords: | kbhowto KB836646 kbAudDeveloper |
---|
|