Considerations for Upgrading SQL Server Management Tools
SQL Server 2008 supports upgrade from SQL Server 2000 or SQL Server 2005. This topic documents support and behavior for upgrading SQL Server Management Tools and management components such as SQL Server Agent, Database Mail, Maintenance Plans, XPStar, and XPWeb.
For local installations, you must run SQL Server Setup as an administrator. If you run SQL Server Setup from a remote share, you must use a domain account that has read and execute permissions on the remote share.
Consider the following issues before you upgrade to SQL Server 2008:
For all upgrade scenarios:
All TSX servers should be upgraded before the MSX server is upgraded. For more information about MSX/TSX in SQL Server, see Automating Adminstration Across an Enterprise in SQL Server Books Online.
All components in an instance of SQL Server must be upgraded at the same time. Version numbers of the Database Engine, Analysis Services, and Reporting Services components must be the same in an instance of SQL Server 2008.
You can add components to an existing installation of SQL Server at the time that you upgrade to SQL Server 2008. For more information, see How to: Upgrade to SQL Server 2008 R2 (Setup).
SQL Server Client Tools, such as SQL Server Management Studio, SQL Server Profiler, the Database Engine Tuning Advisor, sqlcmd, osql, and so on, are not upgraded to SQL Server 2008. Instead, Client Tools run side-by-side with tools from previous SQL Server versions. SQL Server 2008 supports importing settings from earlier versions of SQL Server Client Tools.
Authentication from SQL Server Agent to SQL Server will be updated from SQL Server Authentication to Windows Authentication during upgrade. SQL Server Authentication is not supported in SQL Server 2008.
Data for jobs and alerts will be preserved during upgrade to SQL Server 2008.
If SQLMail is being used in the instance to be upgraded, associated XPs will be supported and enabled after the upgrade. Otherwise, they will be off.
Database Mail, also known as SQLiMail, will be upgraded with the Database Engine component of SQL Server 2008. By default, Database Mail will be off after upgrade. Any schema updates should be reconciled with an update script after upgrade.
Upgrading from SQL Server 2000:
During an upgrade from SQL Server 2000 to SQL Server 2008, all user proxy accounts that existed before upgrading will be changed to the temporary global proxy account UpgradedProxyAccount. The UpgradedProxyAccount is granted access only to those subsystems that were explicitly used, and does not have access to all subsystems after the upgrade is complete.
Although token substitution for SQL Server Agent alerts and job syntax has changed from SQL Server 2000, tokens will not be automatically updated during the upgrade to SQL Server 2008.