Content Management Server 2001 Database Restore Collation Requirements (816844)


The information in this article applies to:

  • Microsoft Content Management Server 2001

SYMPTOMS

When you try to restore a Content Management Server (CMS) database to Microsoft SQL Server, you may experience unpredictable errors. These unpredictable errors occur when a computer that is running SQL Server that you restore the database to has a different collation than a computer that is running SQL Server that the database backup was taken from. These unpredictable errors frequently occur when you try to create objects such as channels, folders, or pages. The unpredictable errors occur because of the way CMS interacts across the databases. The unpredictable errors that you see also depend on the specific collation differences that are discussed in the "Cause" section.

For example, when you try to open an object in Site Builder for CMS 2001, you may receive the following error message:

Failed to Lock Item. Would you like to open it in read-only mode?
You may receive the previous error message although there is no one who is trying to modify the object at the same time that you try to open the object in Site Builder.

CAUSE

When you create a new database on a computer that is running SQL Server, you typically use the default collation. You can back up a CMS database on a computer that is running SQL Server, and then you can restore that database to another computer that is running SQL Server with a different default collation. The problem occurs because the restored database then has a different collation than the computer that is running SQL Server that the database now resides on.

When CMS 2001 uses the CMS database, CMS 2001 also uses other databases in an SQL Server such as the Tempdb database and the Master database. By default, these databases are the same collation as the computer that is running SQL Server that they reside on. If the collation of the CMS database is not exactly the same as the collation of these databases, various unpredictable errors may occur.

RESOLUTION

To avoid this problem, you can setup a computer that is running SQL Server that uses the same collation as the CMS database. Then you can restore the CMS database on this computer that is running SQL Server. This permits you to run Database Configuration Application (DCA) on the destination CMS server to associate it to the newly restored database.

Alternatively, if the size of the exported .rop file for the whole site is 100MB or less (for site deployment best practices), you can use CMS site deployment to export the .rop file from the source server. Then you can import the .rop file to the destination CMS server.

MORE INFORMATION

For additional information about site deployment best practices, click the following article number to view the article in the Microsoft Knowledge Base:

329501 INFO: Best Practices for Performing Site Deployment

STATUS

This behavior is by design. This problem does not affect Content Management Server 2002.
Modification Type:MajorLast Reviewed:7/31/2003
Keywords:kbprb kbinfo KB816844 kbAudITPRO kbAudDeveloper
©2003 Microsoft Corporation. All rights reserved.