Relocating the Logging Database

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

The default RMS configuration places the configuration database and logging database on the same server. Regularly check to make sure that SQL Server has sufficient space available for both the logging and configuration databases.

If the logging database grows too large, you can move it to a different server at any time. It is not possible to relocate the logging database by using the administration Web site; instead, you must do so manually by taking the following steps:

  1. Turn off logging as described in “To Turn On or Off Logging” later in this subject.

  2. Copy the logging database from the source server to the destination server by using SQL Server Enterprise Manager. Make sure that the tables and the stored procedures are created in the new database. One way to do this is by using the SQL Server Enterprise Manager Copy Database Wizard.

  3. Change the configuration database to reflect the new server and database names. In the DRMS_ClusterPolicies table of the configuration database for the cluster for which you are moving the database, do the following:

    • Change the value of the LoggingDatabaseServer policy to reflect the new database server name.

    • Change the value of the LoggingDatabaseName policy to reflect the new database name.

    Note

    SQL Server Enterprise Manager does not work with db_variant fields, so you cannot use it for this task. Instead, you can use Query Analyzer that comes with SQL Server, or another database editing tool.

  4. Restart IIS on all servers that are in the cluster.

  5. Turn logging back on.