How to configure a report server scale-out deployment (Reporting Services configuration)

Reporting Services supports the extended deployment model. This mode allows multiple report server instances that share a single report server database to run.

To create a scale-out deployment, use the Setup program and the Reporting Services Configuration tool:

• Use the Setup program to install each report server instance that will be joined with the scale-out deployment.

• Use the Reporting Services Configuration tool to connect each report server to the shared database. You can only connect and configure a single report server at a time.

• Use the Reporting Services Configuration tool to join the new report server instance to the first Report server instance that is already connected to the report server database to complete the extension.

To avoid database compatibility errors when connecting a server instance to a shared database, ensure that all instances are of the same version. For example, if you create report server data by using a SQL Server 2008 Report Server instance, all other instances in the same deployment must also be instances of SQL Server 2008. For more information, see Configure Reporting Services for a scale-out deployment.

The following instructions explain how to configure a two-node report server scale-out deployment. Repeat the steps that are described in this topic to add additional report server nodes to your deployment.

If you plan to host a scale-out deployment on a Network Load Balancing (NLB) cluster, you should configure the NLB cluster before you configure the scale-out deployment. For more information, see How to configure a report server on a Network Load Balancing cluster.

To install an instance of SQL Server to host the report server database

1. Install the instance of SQL server on the computer that will host the report server database. At a minimum, you need to install the SQL Server Database engine and Reporting Services.

2. If necessary, enable remote connections for the report server. Some versions of SQL Server do not allow remote TCP/IP and Named Pipes connections by default. To confirm that remote connections are allowed, use SQL Server Configuration Manager, and then view the network configuration settings for the target instance. If the remote instance is still a named instance, verify that the SQL Server Browser service on the destination server is enabled and running. SQL Server Browser provides the port number that is used to connect to a named instance.

Install the first Report server instance

1. Installs the first Report server instance that belongs to the deployment content. When you install Reporting Services, on the Report Server Installation Options page, select the install but do not configure server option.

2. Start the Reporting Services Configuration tool.

3. Configure the report Server Web service URL, Report Manager URL, and report server database. For more information, see How to configure a report server in SQL Server Books Online.

4. Verify that the report server is running correctly. For more information, see How to verify Reporting Services installation in SQL Server Books Online.

Install and configure a second report server instance

2. Run Setup to install a second Reporting Services instance on another computer, or install it as a named instance on the same computer. When you install Reporting Services, on the Report Server Installation Options page, select the install but do not configure server option.

4. Start the Reporting Services Configuration tool, and then connect to the new instance that you just installed.

6. Connect the report server to the database for the first Report server instance:

   1. Click Database to open the database page.

   2. Click Change Database.

   3. Click Select an existing report server database.

   4. Type the server name of the instance of the SQL Server database engine that hosts the report server database that you want to use. This server must be a server connected to the instructions above.

   5. Click Test Connection, and then click Next.

   6. In the Report server database, select the database that you created for the first Report server, and then click Next. The default name is ReportServer. Do not select reportservertempdb; it is used only to store temporary data when the report is processed. If your database list is empty, repeat the first four steps to establish a server connection.

   7. On the Credentials page, select the account type and credentials that the report server will use to connect to the report server database. You can use the same credentials as the first Report server instance, or you can use a different credential. Click Next.

   8. Click Summary, and then click Finish.

8. Configure the report Server Web service URL. Do not test the URL first. The URL is resolved after the report server is joined to a scale-out deployment.

10. Configure the Report Manager URL. Do not test the URL first, and do not attempt to validate the deployment. The report server is not available until it is joined to a scale-out deployment.

To join a second report server instance to a scale-out deployment

1. Open the Reporting Services Configuration tool, and then connect to the first Report server instance. Because the first report server has been initialized to perform a reversible encryption operation, it can be used to join other report server instances to a scale-out deployment.

2. Click Expand Deployment to open the scale-out Deployment page. You will see two entries that correspond to the two report server instances connected to the report server database. The first Report server instance should be joined. The second report server should display the status of wait join. If you do not see a similar entry in your deployment, verify that you are connected to the first report server that is configured and initialized to use the report server database.

3. On the scale-out Deployment page, select the report server instance that waits for the join deployment, and then click Add Server.

4. You should now be able to verify that two report server instances are working correctly. To verify the second instance, you can use the Reporting Services Configuration tool to connect to the report server, and then click Web Service URL or Report Manager URL.

If you plan to run a report server in a load-balanced server cluster, additional configuration is required. For more information, see How to configure a report server on a Network Load Balancing cluster.

How to configure a report server scale-out deployment (Reporting Services configuration)