IT professionals will use
Reporting Services Configuration Manager to perform post installation tasks for
SQL Server Reporting Services. Introduced in
SQL Server 2005,
Reporting Services Configuration Manager provides an intuitive interface to perform tasks including specifying the report
server database, report manager url, and indeed one of the first post installation tasks that should be performed is backing up the encryption keys that are used to protect the sensitive information within the rdl files.
Many of the options that are selected within
Reporting Services Configuration Manager are written to a number of configuration files including the rsreportserver.config file located in C:\Program Files\Microsoft
SQL Server\Report
Server InstanceName\Reporting Services\ReportServer folder.When opening this file you will notice that there are more configuration settings within the rsreportserver.config file than is available through the
Reporting Services Configuration Manager Interface. As a result there are additional configuration options that can be defined within this file.
A customer was having a problem performing stress tests against a new Report
Server that would be going live for an enterprise
reporting system. One aspect of the stress test was to fire 50 connections from a single user account. When performing the stress test an error described that the maximum active request had been exceeded. Within the rsreportserver.config, there is a key that is added to the file:
<Add Key=”MaxActiveReqForOneUser” Value=”20”/>
Changing the value from 20 to 50 accommodated the needs of the stress test, however, a wider question should be asked pertaining to this setting when implementing
Reporting Services to a production environment. Within an intranet environment, the default setting is appropriate when network bandwidth is high, users are known and demand for reports is particularly high from a group of users.
However, when deploying a
Reporting Server solution to an extranet, or the internet, you may want to consider reducing this setting to reduce to scope of connections that can be acquired by a single user and placing unnecessary pressure on the report
server. I do hope that
Reporting Services Configuration Manager evolves to include an advanced page that includes an intuitive interface to change configuration settings such as the MaxActiveReqForOneUser, and also configure rendering and data extensions and define secure connection levels to the report
server. All these options can be configured within the rsreportserver.config file, and these are setting that customers would like to see in
Reporting Services Configuration Manager in the future.
If you think that the
SQL community would benefit from this addition, you can vote on it at Microsoft Connect
https://connect.microsoft.com/SQLServer/feedback/details/565575/extending-reporting-services-configuration-manager-rscm
