Databases Reference
In-Depth Information
Hard disk space (by component):
Report Server and Report Manager applications: 50 MB
Microsoft .NET Framework: 100 MB
Samples, AdventureWorks database, and Books Online: 145 MB
Requirements numbers can vary quite a bit from installation to installation, depending on how you
intend to use the service. If you're doing a web farm installation for a heavily used portal, for example,
expect your hardware requirements to go up quickly. If you're unfamiliar with enterprise reporting
installations, it may be helpful to enlist some help from Microsoft or other knowledgeable resource to be
sure you're getting the most out of your investment.
Another useful tool is Microsoft's Baseline Security Analyzer. It can check the security level of your net-
work servers and client machines and is especially handy if you wear multiple hats such as both devel-
oper and server administrator.
Installation Directory
The default installation directory for Reporting Services components is one level below the default loca-
tion of SQL Server:
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
By default, the Report Server is installed one level below that, in the \ReportServer directory. That
folder contains a subdirectory, \bin , where the executables and assemblies are located. You can change
the installation path of the Report Server during setup. Best practice is to use a Secure Socket Layer (SSL)
certificate to create a secure SSL connection across the gap between the reporting service server and
client application.
Service Credentials
At one point during setup, you'll need to provide the credentials used by the Report Server. The user
name and password are used as credentials for the service as it performs tasks and connects to the
Report Server database. You can choose to have the Report Server use a systems account as well. If val-
ues are not provided, then Reporting Services defaults to these settings in the following table.
Operating System
Service Account
Windows XP and 2000
Local System
Windows Server 2003
Network Service
IIS Virtual Directory
A virtual directory is created in Internet Information Services (IIS 5 or greater) to receive incoming HTTP
requests. IIS routes the incoming request to the Report Server, which then processes the data contained
in the body of the request. Once the request has been processed, a response can be sent back to the client
application. The outgoing response is also handled by IIS. The default virtual directory for the Report
Server Web service is:
http://<server_name>/reportserver
Search WWH ::




Custom Search