Monitoring Report Server Performance

Use performance monitoring tools to monitor report server performance to evaluate server activity, observe trends, diagnose system bottlenecks, and gather data that can help you determine whether the current system configuration is adequate. To tune server performance, you can specify how often to recycle the report server application domain. For more information, see Configuring Available Memory for Reporting Services.


Currently, performance counters for the MSRS 2005 Web Service and MSRS 2005 Windows Service are not available for Reporting Services installations on Windows Vista. There is no workaround at this time.

Sources of Performance Data

Use a combination of technologies and tools to get comprehensive information about how the system is performing. Microsoft Windows Server operating systems provide performance information through the following tools:

  • Task Manager
  • Event Viewer
  • Performance console

Task Manager provides information about programs and processes running on your computer. You can use Task Manager to monitor key indicators of your report server's performance. You can also assess the activity of running processes and view graphs and data on CPU and memory usage. For information about using Task Manager, see the Microsoft Windows product documentation.

You can use Performance console and Event Viewer to create logs and alerts about report processing and resource consumption. For information about Windows events that are generated by Microsoft SQL Server 2005 Reporting Services (SSRS), see Windows Application Log in SQL Server 2005 Books Online. For information about Performance console, see "Windows Performance Counters" later in this topic.

SQL Server utilities also provide information about the report server database and temporary databases used for caching and session management. For more information, see Evaluating Performance.

Windows Performance Counters

Monitoring specific performance counters enables you to:

  • Estimate system requirements needed to support an anticipated workload.
  • Create a performance baseline to measure impact of configuration changes or application upgrades.
  • Monitor application performance under certain loads, whether real or artificially generated.
  • Verify that hardware upgrades have the desired impact on performance.
  • Validate changes made to your system configuration have the desired impact on performance.

The two performance objects included with SSRS are:

  • MSRS 2005 Web Service—to monitor report server performance.
  • MSRS 2005 Windows Service —to monitor scheduled operations and report delivery.

The MSRS 2005 Web Service performance object includes a collection of counters used to track report server processing typically initiated through interactive report viewing operations. These counters are reset whenever ASP.NET stops the Reporting Services Web service.

The MSRS 2005 Windows Service performance object includes a collection of counters used to track report processing that is initiated through scheduled operations. Scheduled operations include subscription and delivery, report execution snapshots, and report history.


Custom reporting services performance counters are provided only for MSRS 2005 Web Service and MSRS 2005 Windows Service. Report Manager uses ASP.NET performance counters. For more information, see "Improving .NET Application Performance and Scalability" on MSDN.

If you have multiple report server instances on a single computer, you can monitor the instances together or separately. Choose which instances to include when adding a counter. For more information about using Performance console and adding counters, see the Microsoft Windows product documentation.

In This Section

See Also


Configuring Available Memory for Reporting Services
Administering Reporting Services
Reporting Services Component Overview

Other Resources

Deploying Reporting Services

Help and Information

Getting SQL Server 2005 Assistance