Upgrading Reporting Services
You can upgrade Reporting Services from SQL Server 2000 Reporting Services to the version that ships in SQL Server 2005. How you upgrade depends on the complexity of your installation, whether you are using custom extensions, and whether you have server availability requirements.
Custom installations, Internet-facing installations, and production servers that have up-time requirements require a migration plan that determines in advance the optimal time to perform the upgrade, how best to upgrade the report server database, verification steps that confirm whether the upgrade succeeded, and a backup plan in case the upgrade fails for some unexpected reason. If you are using custom extensions for data processing, delivery, security, or rendering you might need to recompile the extensions before upgrading. If you have a production server, you might want to migrate your installation rather than run an in-place upgrade. You should also consider installing a new instance side-by-side with your existing Reporting Services installation. This allows you to test the installation thoroughly before removing the SQL Server 2000 instance.
Upgrading From SQL Server 2000 to SQL Server 2005
Use the following table to view upgrade options for different deployment scenarios.
| Initial state | Action | State after upgrade |
|---|---|---|
Reporting Services and Database Engine on the same SQL Server 2000 default instance. |
Run Upgrade. Choose the default instance. |
Reporting Services and the Database Engine are upgraded to SQL Server 2005. |
One instance of SQL Server 2000 Reporting Services that runs as the default instance. One instance of the SQL Server 2000 Database Engine that runs as a named instance. Both instances run on the same computer. |
Run Upgrade. Choose the instance you want to upgrade. You can upgrade each instance independently of the other. You can also upgrade all instances at once. |
Separate instances of Reporting Services and the Database Engine, upgraded to SQL Server 2005. Valid combinations include: SQL Server 2005 Reporting Services with SQL Server 2000 Database Engine instance. SQL Server 2000 Reporting Services and SQL Server 2005 Database Engine instance. Reporting Services and the Database Engine both upgraded to SQL Server 2005. |
Upgrading a Single-Server Installation
If you are currently running a default installation that has not been modified, you can upgrade the entire Reporting Services installation by running Setup once. You must be using a local instance of SQL Server Database Engine to host the report server databases. For more information, see Upgrading a Default Installation of Reporting Services.
If you are running a customized installation, you might need to migrate Reporting Services. For more information about migration and upgrade considerations, see Migrating Reporting Services, How to: Install Reporting Services Side-by-Side with an Earlier Version, Using Upgrade Advisor to Prepare for Upgrades, and Breaking Changes in SQL Server 2005 Reporting Services.
Upgrading a Distributed Server Installation
You can configure a Reporting Services installation to host the report server database on a remote computer. You can also configure an installation to run multiple report servers in a scale-out deployment. If you install the report server database on a remote computer, Setup will update the schema for you automatically. If Setup cannot update the schema due to insufficient permissions or connection errors, you must upgrade the report server database manually. For more information, see Upgrading a Report Server Database.
You can upgrade the report server database without upgrading the Database Engine instance that hosts it. If you do upgrade the Database Engine instance, be aware that there are edition requirements for hosting the report server database. For more information about edition requirements, see Creating a Report Server Database. For more information about upgrading multiple report server instances, see Upgrading a Report Server Web Farm.
In This Section
| Topic | Description |
|---|---|
Explains how to enable ASP.NET, start IIS, and configure a report server for local administration on Windows Vista. |
|
Explains how to upgrade an existing Reporting Services installation, where all components are configured to use the default values. |
|
Explains how to upgrade reports that you created in the previous version of Report Designer. |
|
Explains how to upgrade custom assemblies that you deployed in the previous version. |
|
Explains how to modify role-based security settings to use new ad hoc reporting functionality. |
|
Provides information about updating the report server database schema. |
|
Describes the functional differences between the Evaluation and Standard Editions. You can upgrade any edition of Reporting Services, including the Evaluation Edition if it has not expired. |
|
Explains how to upgrade multiple report servers that share a single report server database. |
|
Provides instructions for upgrading an installation that you have modified and installations that consist of components installed on multiple computers. |
See Also
Tasks
How to: Install Reporting Services Side-by-Side with an Earlier Version
Concepts
Installing SQL Server Reporting Services