Microsoft KB Archive/894631

= Using Microsoft Windows SharePoint Services with a content database that is configured as read-only in Microsoft SQL Server =

Article ID: 894631

Article Last Modified on 5/17/2007

-

APPLIES TO


 * Microsoft Windows SharePoint Services
 * Microsoft Windows SharePoint Services 3.0

-



INTRODUCTION
This article discusses using Microsoft Windows SharePoint Services with a content database that is configured as read-only in Microsoft SQL Server. This configuration is a supported configuration. This article also contains a table that lists the issues that users can expect when Windows SharePoint Services uses a content database that is configured as read-only.



MORE INFORMATION
Consider the following scenario. You have a remote server farm and a mirror server farm. You use the Log Shipping feature in SQL Server. The active server farm must be used for authoring, and the mirror server farm must be read-only. You intend to apply log-shipping changes from the active server farm later. In this scenario, you can configure the content database in the mirror server farm for read-only access.

Users can access data in the mirror server farm at the same time that other users access and add data to the active server farm. By doing this, data is available in two different locations. Note that data in the mirror server farm becomes out of date when new data is added to the active server farm or when existing data is modified on the active server farm.

Users will receive error messages when they perform certain operations in Windows SharePoint Services that write information to the read-only database. However, this condition does not affect the read-only databases. You can still apply log-shipping changes from the active server farm to the mirror server farm.

The following table lists the issues that users can expect in Windows SharePoint Services when the content database is configured as read-only.

