eG Help

The report server processes a report in three steps: report processing, data processing, and rendering. Data and report processing are performed on a report definition; the results are in an internal intermediate format. Reports that are in intermediate format are subsequently rendered to a specific viewing format. The following diagram shows the stages and elements of report processing. If there is a slowdown in any of these stages of report processing, it can slow down report execution, which in turn can adversely impact user experience with the SQL Reporting Services.

To ensure high user satisfaction with SQL reporting services, administrators should be able to quickly spot reports that are taking too long to execute, accurately isolate the reason for the slowness, and resolve the bottleneck. This is where the SSRSRespTest test helps!

This test auto-discovers report server users, and for each user, tracks the running time of every report executed by that user. If the execution time of a report exceeds an acceptable, userconfigured running duration, then such a report will be counted as a slow report. The test then reports the count of slow reports per user, and the maximum time spent by every user at different stages of report processing. This way, the test points administrators to the probable cause of the processing bottleneck. Detailed diagnostics provided by the test reveal the exact reports that are slow, and points administrators to the precise reason for their slowness.

Outputs of the test : One set of results for each user of the report server being monitored.

Measurement	Description	Measurement Unit	Interpretation
Reports_executed	Indicates the count of reports that were executed by this user during the last measure period.	Number
Distinct_rprt_executed	Indicates the number of distinct reports that were executed by this user during the last measurement period.	Number	Use the detailed diagnosis of this measure to identify the distinct reports, their current status, and the time each report took to execute. This way, you will be able to tell which report took the longest time to execute. For such a report, the cause for the delay in report execution can also be gleaned from the detailed diagnosis - is it because of slow data retrieval? delayed processing of data? or sluggish rendering?
Max_retrieval_time	Indicates the maximum time taken by the reports of this user for data retrieval.	Seconds	Use the detailed diagnosis of this measure to view the reports that slowed down at data retrieval.
Max_proc_time	Indicates the maximum time taken by the reports of this user for processing.	Seconds	Use the detailed diagnosis of this measure to view the reports that slowed down during processing.
Max_render_time	Indicates the maximum time taken by the reports of this user for rendering.	Seconds	Use the detailed diagnosis of this measure to view the reports that slowed down during rendering.
Slow_reports	Indicates the count of reports that were executing for a duration greater than the configured Report Duration.	Number	Use the detailed diagnosis of this measure to view the slow reports and where the execution bottleneck of each report is - at data retrieval? during report processing? or during report rendering?
Max_duration	Indicates the maximum time taken by reports of this user for execution.	Seconds