Share via

How to: Install Reporting Services Side-by-Side with an Earlier Version

  • Article

You can install multiple versions of Reporting Services, where a SQL Server 2000 Reporting Services instance runs side-by-side with a SQL Server 2005 Reporting Services instance.

Note

If you install the .NET Framework 2.0 or register ASP.NET 2.0 on a server that is running Internet Information Services (IIS) 5.0 or runs in IIS 5.0 compatibility mode, your installation of SQL Server 2000 Reporting Services might stop running. For more information about how to resume server operations, see How to: Troubleshoot Side-by-Side Installations of SQL Server 2000 and SQL Server 2005 Reporting Services.

To run the two versions side-by-side, you must install the SQL Server 2005 version as a named instance, and continue to run the SQL Server 2000 version as the default instance. The SQL Server 2000 version does not support named instances and cannot be configured to run as one.

When running multiple versions of Reporting Services on the same computer, keep the following points in mind:

  • You can use a SQL Server 2000 Database Engine to host a report server database for a SQL Server 2005 Reporting Services installation.
  • The virtual directories must be unique for each report server and Report Manager instance. Consider adding the instance name or version information to each virtual directory name to distinguish each component (for example, ReportServer2005 and Reports2005 for the virtual directories you create for the SQL Server 2005 components).
  • You can use the same Web site for all virtual directories. However, you should create a separate application pool for the SQL Server 2005 report server and Report Manager applications.
  • Report namespaces and SOAP endpoints are different for each version. For more information, see Reporting Services Programmability Enhancements in SQL Server Books Online.
  • Report definition (.rdl) files that you create in the SQL Server 2005 version of Report Designer can only be published to a SQL Server 2005 report server.
  • Report definition (.rdl) files that you create in the SQL Server 2000 version of Report Designer can be published to either a SQL Server 2000 or SQL Server 2005 report server. If you publish a SQL Server 2000 .rdl file to a SQL Server 2005 report server, it will be converted and stored on the report server in the SQL Server 2005 format. If you open a SQL Server 2000 Reporting Services report in the SQL Server 2005 version of Report Designer, you will be prompted to upgrade it. For more information, see Upgrading Reports.
  • The Reporting Services Configuration tool cannot be used to configure a SQL Server 2000 report server. However, you can use Management Studio to connect to a SQL Server 2000 report server. Note that when you install different versions of Reporting Services, each report server installation has a corresponding Report Manager instance that can only be used with that installation. You can expect to see minor differences in the different versions of Report Manager.

You can run newer and earlier versions of Report Designer side-by-side. If you do so, be aware that different versions of Visual Studio must be used (or installed) for each instance:

  • SQL Server 2000 Report Designer requires Visual Studio 2003. It does not run in Visual Studio 2005. You can publish reports from SQL Server 2000 Report Designer to a SQL Server 2005 report server.
  • SQL Server 2005 uses Visual Studio 2005. If you do not have Visual Studio 2005 installed, Setup will install the version of the Visual Studio shell that is necessary for running Report Designer. You cannot use SQL Server 2005 Report Designer to publish reports to a SQL Server 2000 report server.

To Install Reporting Services Side-by-Side With an Earlier Version

  1. Run Setup for SQL Server 2005. When you run Setup, be sure to do the following:

    1. Specify a unique instance name on the Instance Name page or through the instancename option if you are running a command line installation.
    2. Specify a files-only installation for the report server. To do this, select the Install but do not configure option in the Report Server Installation Options page in the SQL Server Installation Wizard or RSCONFIGURATION=filesonly in a command line installation.

  2. After Setup is finished, run the Reporting Services Configuration tool to deploy the new SQL Server 2005 instance.

  3. Connect to the report server instance you just installed. To do so, specify the name of the server and the named SQL Server instance, and then click Connect.

  4. On the Report Server Virtual Directory and the Report Manager Virtual Directory pages, specify a unique virtual directory for the report server and Report Manager. The names cannot be identical to those used in the SQL Server 2000 instance.

    The Windows service and Web service accounts should be configured automatically when you specify the virtual directories. In some cases, automatic configuration might not succeed for the Web service account. If you are using Microsoft Internet Information Services (IIS) 6.0, you can resolve this error by specifying a different application pool.

  5. On the Database Setup page, connect to the SQL Server instance that you want to use to host the report server database. The local Database Engine instance is specified by default. If you want to use another server, you must type the server name. Click Connect to connect to the server.

  6. Click New to create a report server database. In the SQL Server Connection dialog box, type a database name. If you are connecting to a remote SQL Server, specify credentials that have permission to create a database. Click OK.

  7. Optionally, specify credentials that the report server uses to connect to the database. Service account credentials are used by default. Click Apply to save the database configuration changes.

  8. On the Encryption Keys page, create a backup copy of the keys.

  9. To verify the new instance is operational, you can publish sample reports and then view them using Report Manager. Remember to specify the Report Manager virtual directory that you defined for the new instance. For step-by-step instructions on how to publish the sample reports, see the "Configure the report server and install samples" section in the topic How to: Publish Report Samples (Report Designer) in SQL Server Books Online.

See Also

Reference

Instance Name

Concepts

Installing Reporting Services Using Setup
Installing SQL Server Reporting Services

Other Resources

How to: Start Reporting Services Configuration
Configuring Report Server Virtual Directories
Reporting Services Installation How-to Topics
Reporting Services Configuration Tool

Help and Information

Getting SQL Server 2005 Assistance