Before Upgrading: Checklist

The following is a checklist for upgrading:

• Install Microsoft® SQL Server™ version 7.0.
• Back up your SQL Server 6.x database files (all .dat files, including master) so that you can completely restore them if necessary.
• Run the appropriate database consistency checks (DBCC) on the SQL Server 6.x databases to make sure they are in a consistent state.
• Set tempdb to at least 10 MB in your SQL Server 6.x installation (25 MB recommended.)
• Ensure that all database users have logins in the master database.

  This is important for restoring a database because system logins reside in the master database.

• Disable any startup stored procedures.

  The SQL Server Upgrade Wizard starts and stops the SQL Server 6.x server during the upgrade process. Stored procedures processed at startup may cause the upgrade process to hang.

• Ensure that you upgrade all databases with cross-database dependencies at the same time.

  During the version upgrade process, the SQL Server Upgrade Wizard cannot create a login in SQL Server 7.0 for any 6.x logins using default databases that do not exist in SQL Server 7.0.

  For example, you are upgrading three databases, database1, database2, and database4, and there is a login in SQL Server 6.x master..sysdatabases for USER1 that defaults to database3 (not one of the databases you are upgrading). The SQL Server Upgrade Wizard does not create the login because the database is not being upgraded and therefore does not exist in SQL Server 7.0. If USER1 is listed as the owner for objects in any of the databases being upgraded, those objects cannot be created because the login for USER1 does not exist.

• If you are performing a two-computer upgrade, assign a domain username and password to the MSSQLServer service in your SQL Server 6.x and SQL Server 7.0 installations instead of using the local system account or a local user account. The domain user account should belong to the Administrators group of both the computers involved in the upgrade. (The local system account is sufficient for a one-computer upgrade.)
• Stop replication and make sure that the log is empty.
• Shut down all applications, including all services dependent on SQL Server.

If you copied your SQL Server 6.x databases to a new computer to perform the upgrade, you may need to update the new 6.x master database.

• Change references from the earlier server name to the current server name in the 6.x master database.
• Update the device file locations in the SQL Server 6.x master database.
• Make sure all users have corresponding logins.

To change the size of tempdb in SQL Server 6.x

To change to the current server name in the 6.x master database

To update the device file locations in the 6.x master database