You can overwrite an installation of Microsoft® SQL Server™ version 7.0 with a version upgrade to Microsoft SQL Server 2000. If SQL Server 7.0 is detected as an existing installation when you run Setup, you can choose the option to upgrade. In this process, all the SQL Server 7.0 program files are upgraded, and all data stored in SQL Server 7.0 databases is preserved. In addition, SQL Server Books Online for SQL Server 7.0 remains on your computer.
Note SQL Server 7.0 profiler traces and registered servers are not upgraded when SQL Server 7.0 tools are upgraded to SQL Server 2000. Similarly, information models that were installed with Microsoft Repository 2.0 are not upgraded automatically. SQL Server 2000 supports newer versions of information models for both Data Transformation Services (DTS) and the Open Information Model (OIM). For more information about upgrading the DTS information model, see DTS Information Model. For more information about upgrading the OIM, see Upgrading an Information Model.
You can also upgrade from one edition of SQL Server to another edition during the version upgrade to SQL Server 2000. For more information, see SQL Server 2000: Editions and Components.
Caution After you perform this version upgrade, the SQL Server 7.0 installation no longer exists on your computer. The only way to restore an installation of SQL Server 7.0 is to first uninstall SQL Server 2000, perform a complete reinstall of SQL Server 7.0 files, and then restore your backed-up SQL Server 7.0 databases.
To upgrade an installation of SQL Server 7.0 to SQL Server 2000
After you upgrade from SQL Server 7.0 to SQL Server 2000, it is recommended that you repopulate full-text catalogs and update statistics. Both operations can be time-consuming, but will enhance the performance of SQL Server 2000.
The upgrade process marks your databases as full-text disabled, due to a format change from SQL Server 7.0 to SQL Server 2000. Catalogs must be repopulated after an upgrade, but this operation is not automatically run at setup time because it can be time-consuming. Administrators should plan to repopulate all full-text catalogs at a convenient time. For more information, see sp_fulltext_catalog and sp_fulltext_database.
It is recommended that you update all SQL Server 7.0 statistics after upgrading to SQL Server 2000. Although this update may take a significant amount of time on large databases, using SQL Server 7.0 statistics with SQL Server 2000 may result in poor query performance.
Use the sp_updatestats stored procedure, to update statistics in user-defined tables in SQL Server 2000 databases. For more information, see sp_updatestats.
How to repopulate all full-text catalogs for a database (Enterprise Manager)