views:

2405

answers:

2

We are experiencing a slow start up time on the first report request of the day, or when there have been no report requests for an unknown period of time. In SQL Reporting Server 2005 installations we would set up the App Pool to avoid recycling the Reporting Services applications.

However, my client installed SQL Reporting Server 2008 on Windows Server 2008 in Native mode. There is no IIS installation that I can locate. I've checked through the SQL Reporting Service Configuration Settings, the Help files and forums and have not located a solution for this problem on a Native installation.

How can I control the recycling of the Reporting Services application when installed in Native mode?

+1  A: 

I believe the solution is to add a ProcessTimeout key in the rsreportserver.config file. There is this key in this file from the default installation but it is commented out. I'm not sure if this is minutes or seconds, but I modifed it to 28800 and the process was still running first thing this morning after no activity for over 12 hours. The first report loaded in a few seconds.

The file is located in ~/program files/microsoft sql server/msrs10.mssqlserver/reporting services/reportserver

I also modified the 7200 in this file.

+4  A: 

I did not find the parameter referenced in tcc'sresponse. However his response did clue me in to the existence of configuration file; I did find a page that had detail on the contents:

MSDN: How to: Modify a Reporting Services Configuration File

In it I found the RecycleTime parameter. It defaults to 720 which feels like the 20 minutes or so it took to time out. I set it to 28800.

I restarted the Reporting Services service for good measure, and accessed the site. It took the usual minute or two to come up and during that time the server was working hard. It is snappy now; I will test throughout the day to see if this keeps Report Services from recycling the process and rebuilding every 20 minutes and report back to this site.

jlo
This appears to have solved my problem.
jlo
The parameter is in minutes. 28800 = 480 hours!http://msdn.microsoft.com/en-us/library/ms157273.aspx
matt eisenberg
Thank you so much. This also helps (I needed both) http://stackoverflow.com/questions/784918/asmx-web-service-slow-first-request/784947#784947
Praesagus
Thanks for the help on this. @matt is 480 hours a bad thing??? are there bugs(memory leaks) in SSRS that require it to be shutdown every 12 hours?
Eric Labashosky