Microsoft KB Archive/310819

= DOC: Only Cached Objects Are Available During Site Deployment Import =

Article ID: 310819

Article Last Modified on 10/29/2007

-

APPLIES TO


 * Microsoft Content Management Server 2001 Enterprise Edition
 * NCompass Resolution 4.0

-



This article was previously published under Q310819



SUMMARY
Chapter 7 of the Microsoft Content Management Server 2001 Site Administrator's Guide and chapter 7 of the NCompass Resolution 4.0 Site Management Guide state the following:

Use Site Deployment Manager when it causes the least amount of inconvenience to the users on your site. Moving parts of your site may take time, and Site Deployment Manager locks out modifications to the destination system (the server you are transferring objects to) during this period. This prevents users from making modifications to objects in the destination server; however they still have read access to the destination server.

It is important to note that read access to the destination server is available only to those objects that are already in the disk cache before the site-deployment import operation begins.



MORE INFORMATION
During the site-deployment import operation, the Content Management Server (CMS) database is locked; neither read nor write access to the database is available during the import process. This prevents users from making modifications to the CMS server that the site is being deployed to. Any requests for CMS objects that are made while the import process is taking place are directed to the disk cache. For example, if a user browses to a posting on the CMS server while a .rop file is being imported, that user sees the cached version of the posting. If no cached version exists, the posting is unavailable until after the import operation is complete.

The documented Best Practices dictate that you use the Site Deployment Manager when it causes the least inconvenience to the users who are accessing your site.

Note The resolution that is described in this article has been confirmed on a single CMS server on which IIS was not being used by other server products, Web applications, or Internet technologies such as Microsoft Site Server, Microsoft Commerce Server, Microsoft Application Center, or ASP fragment caching.

