In-Place Upgrade

In-Place Upgrade:

Once we’ve run the Upgrade Advisor and after upgrading SSAS, we can upgrade to SQL Server 2008. The following steps are from upgrading a SQL Server 2000/2005 instance to SQL Server 2008.

1. Launch the SQL Server Installation Center as shown in the screenshot, either by running setup.exe or double-clicking the SQL Server 2008 installation media. If we did not run Upgrade Advisor, we may be prompted to install .NET Framework 2.0 and Windows Installer 4.5.
2. Click Installation on the left hand side and then Upgrade from SQL Server 2000 or SQL Server 2005. The installation routine checks whether the SQL Server 2000/2005 host server meets the minimum requirements for setup. If the routine check finds a problem at this stage, we should quit the installer, solve the problem, and then restart the upgrade.
3. Enter the license key and accept the license terms. Click on install on the next screen to install the setup support files.
4. On the Select Instance page, select the instance of SQL Server 2000/2005 that we need to upgrade.
5. By default, the SQL Server 2000/2005 Database Engine, SQL Server Replication, Full-Text Search, SSAS, and Management Tools will be upgraded. It’s not possible to deselect any of these features if we choose the full upgrade option. If we choose to upgrade shared features, we can upgrade only the shared features.
6. On the Instance Configuration page, select the instance ID and click Next.
7. When we reach the Disk Space Requirements page, the upgrade routine checks whether enough space is available for the upgrade. The upgrade needs about 2GB of space; approx. 700MB on the system drive, 600MB on the drive hosting the program files, and another 700MB on the drive hosting the instance we are upgrading.
8. On the Service Accounts page, the SQL Server Browser service will be specified by default to NT AUTHORITY\LOCAL SYSTEM. In general, we should use a separate, specially named, low privilege account for each service.
9. On the Full-text Upgrade page, we can choose to import, rebuild, or reset full-text catalogs. Importing is the quickest, but that option doesn’t use the new and enhanced SQL Server 2008 word breakers, which determine where boundaries between words in text exist. The Rebuild option uses the enhanced word breakers but might incur a performance hit. The best option in many cases is Reset, which removes the catalog files but keeps metadata for catalogs and indexes. The catalog will remain empty when the upgrade is completed.
10. On the Error and Usage Reporting page, specify whether we need to send Windows and SQL Server error reports to Microsoft or not. The options are disabled by default.
11. The Upgrade Rules page shows the results of tests that the installation routine performs. This check is less thorough than the one performed by Upgrade Advisor.
12. The routine then provides a summary of our upgrade information and displays the path to the upgrade configuration file. Click Upgrade to start upgrading to SQL Server 2008. Depending on our hardware configuration, the upgrade process will continue from several minutes to hours. The database is unavailable to clients during the upgrade process.
13. When the upgrade is finished, the wizard tells us the upgrade status of each component. The final page of the upgrade wizard shows the location of the upgrade log.