Rediger

Del via


Monitor report server performance

Applies to: SQL Server 2016 (13.x) Reporting Services and later  Power BI Report Server

Use performance monitoring tools to monitor report server performance to evaluate server activity, watch trends, diagnose system bottlenecks, and gather data that can help you determine whether the current system configuration is sufficient. To tune server performance, you can specify how often to recycle the report server application domain. For more information, see Configure available memory for report server applications.

Sources of performance data

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

  • Task Manager

  • Event Viewer

  • Performance Monitor

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 Event Viewer and Performance Monitor to create logs and alerts about report processing and resource consumption. For information about Windows events that Reporting Services generates, see Windows application log. For information about Performance Monitor, see "Windows Performance Counters" later in this article.

SQL Server utilities, such as SQL Server Profiler or Extended events, also provide information about the report server database and temporary databases used for caching and session management.

Windows performance counters

Monitoring specific performance counters enables you to:

  • Estimate system requirements needed to support a predicted workload.

  • Create a performance baseline to measure effect of configuration changes or application upgrades.

  • Monitor application performance under certain loads, whether real or artificially generated.

  • Verify that hardware upgrades have the desired effect on performance.

  • Validate changes that were made to the system configuration have the desired effect on performance.

Reporting Services performance objects

SQL Server 2016 Reporting Services includes the following performance objects:

  • MSRS 2016 Web Service and MSRS 2016 Web Service SharePoint Mode to monitor report server performance. These performance objects include a collection of counters used to track report server processing typically initiated through interactive report viewing operations. These counters are reset whenever the Report Server Web service is stopped or recycled.

  • MSRS 2016 Windows Service and MSRS 2016 Windows Service SharePoint Mode to monitor scheduled operations and report delivery. These performance objects include 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.

  • ReportServer:Service and ReportServerSharePoint:Service to monitor HTTP-related events and memory management. These counters are specific to Reporting Services, and they track HTTP-related events for the report server, such as requests, connections, and sign in attempts. This performance object also includes counters related to memory management.

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 you add a counter. For more information about using Performance Monitor (perfmon.msc) and adding counters, see the Microsoft Windows Performance Monitor product documentation.

Other performance counters

Custom Reporting Services performance counters are provided only for the Reporting Services performance objects listed earlier in this article. The following .NET Framework performance objects provide more performance monitoring data for the report server.

Note

Power BI Report Server and SQL Server Reporting Services 2017 and later don't include Reporting Services performance objects. There are .NET Framework performance counters available to provide performance monitoring for the report server.

Performance object Notes
.NET CLR Data and .NET CLR Memory The web portal uses ASP.NET performance counters. For more information, download Improve .NET application performance and scalability.
Process Add the Elapsed Time and ID Process performance counters for a ReportingServicesService instance to track process uptime by process ID.

SharePoint events

In addition to the Reporting Services performance objects, you might also want to configure SharePoint events. You might want to configure events this way if you're running a report server in SharePoint integrated mode and configured your reporting environment to use a SharePoint product. In this section, use the Events for a Report Server in SharePoint Integrated Mode to review diagnostic events that might provide useful information if your reporting environment is integrated with SharePoint.

In this section

Performance counters for the MSRS 2016 Web Service and MSRS 2016 Windows Service performance objects (native mode)
Describes the performance counters used by the Report Server Web service.

Performance counters for the MSRS 2016 Web Service SharePoint Mode and MSRS 2016 Windows Service SharePoint Mode performance objects (SharePoint mode)
Describes the performance counters used by the Report Server Windows service.

Performance counters for the ReportServer:Service and ReportServerSharePoint:Service performance objects
Describes the HTTP-related and memory-related performance counters in Reporting Services.