Upgrading Editions of Reporting Services

This topic describes requirements and considerations when upgrading between some editions of Reporting Services. The upgrading scenarios that are discussed in this topic include the following:

  • Upgrade paths for different versions and editions of Reporting Services.
  • Upgrading to editions that have more features (for example, from Standard Edition to Developer or Enterprise Editions).
  • Upgrading to editions that have fewer features (for example, from Evaluation to Standard Edition).

You can also upgrade from SQL Server 2005 Express Edition with Advanced Services (SQL Server Express) to other editions. For more information, see How to: Upgrade a SQL Server Express Report Server to Another SQL Server Edition and Reporting Services in SQL Server 2005 Express Edition with Advanced Services in SQL Server Books Online.

Upgrading from SQL Server 2000

The following table shows the possible upgrade paths from SQL Server 2000 editions to SQL Server 2005 Reporting Services.

SQL Server 2000 Edition SQL Server 2005 Edition




Standard, Developer, Enterprise





Other upgrade paths are possible (for example, upgrading from the Developer Edition directly to the Enterprise Edition of SQL Server 2005), but Setup will not perform all of the steps for you automatically. In this case, you can install a new instance of the edition you want to use, and then move the report server database to the new installation. For more information, see Migrating Reporting Services.

Upgrading the Evaluation Edition

To upgrade the Evaluation Edition, it must not be expired. If your evaluation copy has expired, you can install a new edition and then configure the new report server instance to use the existing report server database. If your evaluation copy of the software has not expired, you can use Setup, but the upgrade must be performed as a two-step operation:

  1. Upgrade SQL Server 2000 Evaluation Edition to SQL Server 2005 Evaluation Edition.
  2. Upgrade SQL Server 2005 Evaluation Edition to any other SQL Server 2005 Edition.

Upgrading Editions Within SQL Server 2005

You can upgrade editions within the same version of SQL Server. The following table shows the upgrade path for different editions of SQL Server 2005 Reporting Services. Each edition has software requirements that must be satisfied. An upgrade might not succeed if your system does not meet the minimum software requirements of the new edition. For more information, see Version and Edition Upgrades.

SQL Server 2005 SQL Server 2005


Express, Workgroup, Standard, Developer, Enterprise


Workgroup, Standard, Developer, Enterprise


Standard, Developer, Enterprise


Developer, Enterprise


Workgroup, Standard, Enterprise

Upgrading to Editions that Have More Features

If you have an existing installation of Reporting Services Standard Edition, Express Edition, or Workgroup Edition, you can run Setup to upgrade to the Developer or Enterprise Editions. These editions include additional features. There is no feature reduction in the edition upgrade. All reports, models, and applications that you created in the Standard Edition will continue to work in the upgraded edition. For more information, see Features Supported by the Editions of SQL Server 2005.

Upgrading to Editions that Have Fewer Features

If you are upgrading the Evaluation Edition to the Standard Edition or Workgroup Edition, the following features will no longer be available in the upgraded edition:

  • Data-driven subscriptions
  • Report server scale-out deployment
  • Support for more than four processors

If you used any of these features in the Evaluation Edition, read the following section to determine the effect on existing files and functionality when you upgrade to the Standard Edition.

Data-Driven Subscriptions

Data-driven subscriptions are deactivated (that is, they no longer run) but not deleted. You must delete the subscriptions manually. For more information, see Creating, Modifying, and Deleting Data-Driven Subscriptions.

Report server scale-out deployment

If you upgrade a report server instance in scale-out deployment to the Standard Edition, the report server instance you upgraded will no longer work. If you had two report server instances sharing a single report server database, you must now have a separate report server database for each instance. To use the upgraded report server, you can choose between these options:

  • Create a new report server database for the report server instance that is no longer part of the scale-out deployment. For more information, see Creating a Report Server Database.
  • Make a copy of the existing report server database, attach it, remove the key information, and then configure the upgraded report server to use it. For more information, see Migrating Reporting Services.
  • Continue to use the existing report server database with the upgraded report server. You can do this by removing the key information that was created for other report server instances in the deployment. To remove key information for report server instances that are no longer part of a scale-out deployment, you can use the Initialization page in the Reporting Services Configuration tool. For more information, see Adding and Removing Encryption Keys for Scale-Out Deployment and Initialization (Reporting Services Configuration).

Support for more than four processors

Setup will not upgrade an existing installation running on more than four processors to the Standard Edition. You must install a new instance and then migrate your installation.

See Also


Upgrading Editions of Reporting Services
Upgrading a Report Server Web Farm

Help and Information

Getting SQL Server 2005 Assistance

Change History

Release History

14 April 2006

New content:
  • SQL Server 2005 Express Edition with Advanced Services