Database Configuration

Before any data is transferred, the SQL Server Upgrade Wizard creates, if necessary, database and log files large enough to contain the upgraded database data. You have several options for creating the Microsoft® SQL Server™ version 7.0 database and log files.

Using the Default Database Configuration

The SQL Server Upgrade Wizard estimates how much space is necessary to hold transferred objects and data for each selected database and creates database files of the estimated sizes. The wizard makes no allowance for free space beyond the loaded data. By default, the data file for a database is placed in the same location as the first device used by that database in SQL Server 6.x.

The SQL Server Upgrade Wizard also creates a log file for each database using the SQL Server 6.x log size. By default, the log file is placed in the same location as the first device used for log space in SQL Server 6.x.

You can view and edit the default database configuration in the SQL Server Upgrade Wizard. For each database and log file you can modify:

If the 6.x database(s) used multiple devices, multiple database files will be created in the same locations. However, the first database file will be sized to accommodate the bulk of the data and the other files will be minimally sized. If you want to remove these files you must do so before they are created. All files are set to grow automatically if extra space is required.

Using a Custom Database Configuration

You can specify your own configuration in one of two ways:

If you create the user databases or an SQL script file, the SQL Server 7.0 databases must have the same names as in SQL Server 6.x. Also, remember that data may take up more disk space in SQL Server 7.0 than in SQL Server 6.x. The SQL Server Upgrade Wizard estimates this growth. Click Edit to view the default configuration to see the estimated initial size of the SQL Server 7.0 databases. It is recommended that you leave the autogrow feature on for each database. You may also want to set a backward compatibility level for each database.

To edit the default database configuration

See Also
Estimating the Disk Space Required for Upgrading CREATE DATABASE
Backward Compatibility  

  


(c) 1988-98 Microsoft Corporation. All Rights Reserved.