>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

"Tony" <Tony@discussions.microsoft.com> wrote in message
news:35CB04BD-BB0B-4D38-A4FF-03A52557E4A3@microsoft.com...
> Hi All,
>
> Everytime when I run the report (by URL access), it need a very long time
> to
> wait. After such init step, then it return normal speed when I run
> another
> report!
>
> Anyone can help ! Thanks!
>
> Tony
>

"Bruce L-C [MVP]" wrote:

> I noticed this when I first started with RS and what I did to get around it
> is to have a report open on my desktop that auto executes every 5 minutes,
> this keeps this going. I have been told that the below will work. If you
> want to do my way then get a simple report, in report->properties set it to
> refresh every 5 minutes (or 10 or 15, whatever).
>
> Here is what Chris suggests:
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> If you are running Windows 2003 server for your IIS reportserver, then this
>
> is a simple issue - I'll explain what happens:
>
> The report service engine, once it is idle for more than the default 20
>
> minutes, the worker process is shutdown.
>
> This is controlled by IIS.
>
> Open up the Internet Information Services (IIS) Manager
>
> Expand the server node then the application pools.
>
> On my IIS machine, I created an application pool dedicated to the
>
> reportserver & reportmanager virtual webs.
>
> But anyways, for the application pool that the reportserver is pointing to
>
> if you left everything to their defaults will be the DefaultAppPool.
>
> Right click the default app pool and select properties.
>
> There are two things that are checked by default - On the recycling tab
>
> there is a checkbox for recycling worker processes - it is currently set to
>
> 1740 minutes (29 hours). Leave it.
>
> The other one is on the performance tab - which is the one you are
>
> interested in changing....
>
> See the "Idle Timeout" section and increase the number of minutes to be 8
>
> hours a typical working day - 8*60 = 480 minutes.
>
> Next, to be sure the "morning person" that runs the first report doesn't get
>
> the delay, set up a schedule for either a dummy or adhoc report to fire off
>
> like at 6am so that the report component worker processes get loaded.
>
> I hope this helps you.
>
> There is no need to have a report fire off every minute to keep things
>
> alive - it is just that the report service was "unloaded" and needed to load
>
> back up.
>
> =-Chris
>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
>
>
> "Tony" <Tony@discussions.microsoft.com> wrote in message
> news:35CB04BD-BB0B-4D38-A4FF-03A52557E4A3@microsoft.com...
> > Hi All,
> >
> > Everytime when I run the report (by URL access), it need a very long time
> > to
> > wait. After such init step, then it return normal speed when I run
> > another
> > report!
> >
> > Anyone can help ! Thanks!
> >
> > Tony
> >
>
>