Before beginning the site upgrade process, you should test the site database upgrade process on a copy of the Microsoft Systems Management Server (SMS) 2003 site database to be upgraded. To test the database for an upgrade, you use the /testdbupgrade setup command-line switch, as in the following example:

  Copy Code 
Setup /testdbupgrade SMS_<sitecode>

When this command is run, the setup Prerequisite Checker will launch and verify that the database to be tested meets the requirements for the test. The test must be run on a supported version of Microsoft SQL Server 2005, and SQL Server database replication must not have been configured for the database before it was copied or backed up in preparation for the test. The results of the prerequisite check can be viewed in the ConfigMgrPrereq.log log file created in the root of the system drive.

Note
The database upgrade test fails on SMS site databases that are copied or restored from an SMS 2003 site database with SQL Server database replication enabled. This is because when SQL Server database replication is enabled for the SMS 2003 site database, the computer running SQL Server modifies the SQL Server tables that are included in the publication. When the database is restored to another database, the setup /testdbupgrade fails on that restored SMS site database.

After the setup Prerequisite Checker has successfully verified that all prerequisites for the test are met, the database is tested for upgrade. The actions taken, and their results, can be viewed in the ConfigMgrSetup.log log file created in the root of the system drive.

If the database upgrade test is successful, you can be assured that the database portion of the upgrade process will be successful. Any problems you encounter during the test must be corrected before you upgrade your production site database. If this test fails, the database is incompatible with Configuration Manager 2007, and a clean installation will be required.

Caution
After running the Setup /testdbupgrade setup switch, your SMS site database will not be compatible with earlier versions of SMS if you do not complete the upgrade. Be sure to run this test on a copy of your SMS 2003 site database rather than on the original.

Use one of the procedures below to test the site database for upgrade, depending on the version of SQL Server hosting the site database to be tested.

Note
For a list of supported SQL Server versions, see Configuration Manager Supported Configurations.

To test an SMS 2003 site database hosted by SQL Server 2005 for upgrade by copying the database

  1. Record the size of the SQL Server data and log files. You will need to compare these sizes to the sizes of the files after the database upgrade test has completed.

  2. On the SQL server hosting the site database, log in to Microsoft SQL Server Management Studio and ensure that the SQL Server Agent is running.

    Note
    The SQL Server Workstation Components must be installed on the SQL server to start SQL Server Management Studio.

  3. Ensure that SQL Server is configured to autogrow and that sufficient disk space is available on the computer running SQL Server to complete the test successfully. (Depending on the size of your current site database, the required disk space amount will vary.)

  4. If required, disable SQL Server replication for the site database.

  5. Use the Copy Database Wizard to copy the site database. To start the Copy Database Wizard in SQL Server Management Studio, right-click <site database name>, click Tasks, and then click Copy Database.

    Note
    You can schedule the copy to run immediately or at a later time. You can also copy the database to the local database server or a different SQL Server machine. It is recommended to copy the database to a remote SQL Server machine not hosting a site database to perform this procedure.

  6. Open a command prompt, navigate to the Configuration Manager setup files directory on the SQL Server computer hosting the database copy, and enter the following text: setup.exe /testdbupgrade <copied database name>.

  7. Review the ConfigMgrPrereq.log and ConfigMgrSetup.log log files, located at the root of the system drive, to verify that the test database upgrade was successful. Any problems encountered during the test upgrade must be corrected before you upgrade your production site database.

  8. Record the size of the SQL Server data and log files, and compare them to the sizes you recorded in step 1. This will determine the amount of disk space required for a successful site database upgrade.

To test an SMS 2003 site database hosted by SQL Server 2000 for upgrade by restoring a site database backup to a remote computer running SQL Server 2005

  1. Record the size of the SQL Server data and log files. You will need to compare these sizes to the sizes of the files after the database upgrade test has completed.

  2. Ensure that SQL Server is configured to autogrow and that sufficient disk space is available on the computer running SQL Server to complete the test successfully. (Depending on the size of your current site database, the required disk space amount will vary.)

  3. If required, disable SQL Server replication for the site database.

  4. Back up your SMS 2003 site database using the SMS site backup maintenance task. To force an immediate site backup, run the command net start sms_site_backup from a command prompt.

    Note
    Alternatively, you can stop all SMS services on the SMS site server and SQL Server, and then use SQL Server Enterprise Manager to back up the SMS site database.

  5. Copy the site database backup to a different computer running SQL Server 2005.

  6. Manually create a new database on the SQL Server 2005 computer with the same name as the one you backed up, and restore the database backup to it.

  7. Open a command prompt, navigate to the Configuration Manager setup files directory, and enter the following text: setup.exe /testdbupgrade <database name>.

  8. Review the ConfigMgrPrereq.log and ConfigMgrSetup.log log files, located at the root of the system drive, to verify that the test database upgrade was successful. Any problems encountered during the test upgrade must be corrected before you upgrade your production site database.

  9. Record the size of the SQL Server data and log files, and compare them to the sizes you recorded in step 1. This will determine the amount of disk space required for a successful site database upgrade.

See Also