Part 3 – Configuring SQL Server Reporting Services in Windows Server 2008
In our previous articles, we have seen how to install SQL Server Reporting Services and to create a new report using the Report Wizardand Report Designer Window. Now, in this article we are going to see how to configure SQL Server Reporting Services in Windows Server 2008 environment.
To deploy the report on a server and to use it across the environment we need to have the Report Server up and running. To do so we need to do some configuration for the report server. It will be covered in this article. Let us see the step-by-step process on the configuration of the SQL Server Reporting Services.
Considering that SQL Server Reporting Services (Denali or 2008 R2) is installed, we will step forward to do the configuration. Go to All Programs>> Microsoft SQL Server 2008 >> Configuration Tools>> Reporting Services Configuration Manager as shown in the screen below.
The Reporting Services Configuration Manager will open as shown in the screen below.
Now we need to connect to the instance on which we need to configure the SQL Server Reporting Services. A pop-up window will appear prompting to select the Server Name and Instances Name. Select the appropriate Server and Instance Name and click on Connect as shown in the screen below.
Once connected successfully, we can see the Reporting Services instance running and option to start and stop the services. In addition, we can also see the details of the server running as shown in the screen below.
Now click on the Service Account on the left side menu to configure the account details. Here, we have two options to select the account details. If our server is domain controlled then we will go ahead with selecting the domain user name and password. Else, we can use the built-in account as shown in the screen below. Once we select the account click on Apply button to save the configuration.
Once we are done with the above configuration, click on to the next menu Web Service URL to configure the Virtual Directory. We can configure the virtual directory with any customized name or we can use the default name ReportServer and use the default configurations as shown in the screen below. Once we are done with the above configurations, click on Apply button to save the configurations
Now click on the next menu Database to create a new database or use an existing database for the SQL Server Reporting Services for saving all the reporting server data and application data for running the reports. Click on Change Database to select the database as shown in the screen below.
Once we click on the Change Database button, a new pop-up window will be displayed to configure the database. Here, we can select to either create a new database or use existing database as shown in the screen below.
Follow the basic steps used to create the database. Once the default steps are passed, we can see that the database is created as shown in the screen below.
Now click on Finish button. We will see the database selected and the login details on to the main wizard as shown in the screen below. Once the required changes are done for the database, click on Apply to save the database configurations.
Now go to the next menu Report Manager URL and select the Virtual Directory. Name it as per the requirement, else by default we can use the one created by the server (Report) as shown in the screen below. Click on Apply once we are done with the configuration.
Now we are done with all our configurations. To check if the configurations are done perfectly we need to navigate to
http://<Servername>/Reports and check. Since in our article we have used the built in server we will try with
If the configurations are done correctly, we will see the Report Server screen as shown in the screen below.
In the above screen, we can see some of the projects deployed to the server, which we will cover in our next article.
Therefore, in this article we have seen how to configure the reporting services on to windows server 2008 server. In our next article, we will see how to deploy the Reporting project, which we created in Part 2 of this series.