RS2005 - Response Time

When running a report in VS, the report run fast but when running the same
report via the browser (<servername>\reportserver), the report runs slow.
How can I increase the response time in running the report via the browser?
Thank you.One thing to remember, in VS it caches the data (look in your directory and
you will see a .data file). So sometimes this can give you an erroneous idea
of the time required.
Also, if it is the first time that RS has run in awhile you will get a big
delay. So run any report to make sure RS is up and active and then run your
report you are concerned about.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Terry" <Terry@.discussions.microsoft.com> wrote in message
news:BB36DBF2-4F3C-4BF7-8850-6CCC9639FE7C@.microsoft.com...
> When running a report in VS, the report run fast but when running the same
> report via the browser (<servername>\reportserver), the report runs slow.
> How can I increase the response time in running the report via the
> browser?
> Thank you.|||Do you know what 'awhile' is? Is it possible to run a schedule report
just to keep RS 'alive'?
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
news:uRucKBj3FHA.3708@.TK2MSFTNGP10.phx.gbl:
> One thing to remember, in VS it caches the data (look in your
> directory and you will see a .data file). So sometimes this can give
> you an erroneous idea of the time required.
> Also, if it is the first time that RS has run in awhile you will get a
> big delay. So run any report to make sure RS is up and active and then
> run your report you are concerned about.
>|||I have a simple report I keep open on my desktop that autoexecutes every 5
minutes. You could also try Chris' suggestion posted below:
>>>>>>>>>>
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
"Asher_N" <compguy666@.hotmail.com> wrote in message
news:Xns97009891877C1compguy666hotmailcom@.207.46.248.16...
> Do you know what 'awhile' is? Is it possible to run a schedule report
> just to keep RS 'alive'?
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
> news:uRucKBj3FHA.3708@.TK2MSFTNGP10.phx.gbl:
>> One thing to remember, in VS it caches the data (look in your
>> directory and you will see a .data file). So sometimes this can give
>> you an erroneous idea of the time required.
>> Also, if it is the first time that RS has run in awhile you will get a
>> big delay. So run any report to make sure RS is up and active and then
>> run your report you are concerned about.
>>
>|||"Bruce L-C [MVP]" <brucelc@.newsgroup.nospam> wrote in
news:#wuXBil3FHA.3292@.tk2msftngp13.phx.gbl:
> I have a simple report I keep open on my desktop that autoexecutes
> every 5 minutes. You could also try Chris' suggestion posted below:
>>>>>>>>>>
> 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
>>>>>>>>>>
>
Thanks