Databases Reference
In-Depth Information
Summary
Microsoft has improved the management tools in this edition of Reporting Services, making server
administration mostly straightforward. How you configure your Reporting Services environment will
affect the number of incoming requests your servers can handle.
To increase the capacity of your report server, one of the first things to look at is deploying the
ReportServer and ReportServerTempDB databases to a remote instance of SQL Server.
Some other things to keep in mind when considering a Reporting Services deployment include:
❑
As much as possible, render reports from cached data rather than live data.
❑
Be reasonable when defining report requirements. Large, complex reports consume server
resources and may not be the best way to meet user needs.
❑
Use scheduling to process reports during off-peak times to reduce anticipated server loads.
❑
Use tools such as Query Analyzer and SQL Profiler to improve query performance.
❑
Consider linked reports to reduce database round trips. Linked reports can provide users with a
subset of data by leveraging the filtering, grouping, and aggregate function capabilities of the
report server.
Lastly, consider scaling out in addition to scaling up. If you'll remember, scaling up is the addition of more
capacity within a server. For example, by adding processors to create dual- or quad-processor machines.
Scaling out is adding more machines to spread the load and has been popular for Reporting Services
installations. Scaling out can be a flexible, cost-effective way of incrementally adding and removing
additional capacity. When anticipating a seasonal spike in reporting loads, for example, adding relatively
inexpensive commodity servers will not only help balance the load but will also provide an additional
degree of fault tolerance.
The next chapter takes a closer look at working programmatically with the report server, to enable viewing
reports in custom client applications.
Search WWH ::
Custom Search