Report Manager slow to open

I have been trying various things I have read about in order to solve
the problem of Report Manager being very slow to open for the first
user. I have set the Idle Timeout section in IIS to 480 minutes. I have
created a scheduled report to run every 8 hours. (My client is a 24/7
organization.) I read somewhere that a fix was to refresh a report
every five minutes. I'm not sure how to refresh a report, but I did set
a snapshot to run every hour.
Setting the Idle Timeout to 480 minutes means that within an 8 hour
period the problem is solved. But there is still the problem of the
very slow open for the first user of the shift.
Creating the scheduled report and setting the snapshot have not solved
the problem. I am using Reporting Services 2000 and the scheduled
report and snapshot both contain no data because this client is
connecting to Access databases rather than SQL Server and the Access
database causes problems with both the schedule and the snapshot. Any
suggestions of what I can do to not cause the first user of the shift
to wait a minute or longer for Report Manager to open?
Thanks very much.
LisI would have thought that running a scheduled report every hour would work.
However, I guess because it returns nothing then it isn't doing what it
needs to do to wake up. Before I knew about the IIS configuration (which you
have done) I had a report open on my desktop and I set it to refresh. I did
it every 5 minutes because it was data I wanted to see. You obviously do not
have to have it do that. In layout, Report Menu-> Report Properties.
AutoRefresh
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<info@.techknowsolve.com> wrote in message
news:1168387368.490665.23570@.77g2000hsv.googlegroups.com...
>I have been trying various things I have read about in order to solve
> the problem of Report Manager being very slow to open for the first
> user. I have set the Idle Timeout section in IIS to 480 minutes. I have
> created a scheduled report to run every 8 hours. (My client is a 24/7
> organization.) I read somewhere that a fix was to refresh a report
> every five minutes. I'm not sure how to refresh a report, but I did set
> a snapshot to run every hour.
> Setting the Idle Timeout to 480 minutes means that within an 8 hour
> period the problem is solved. But there is still the problem of the
> very slow open for the first user of the shift.
> Creating the scheduled report and setting the snapshot have not solved
> the problem. I am using Reporting Services 2000 and the scheduled
> report and snapshot both contain no data because this client is
> connecting to Access databases rather than SQL Server and the Access
> database causes problems with both the schedule and the snapshot. Any
> suggestions of what I can do to not cause the first user of the shift
> to wait a minute or longer for Report Manager to open?
> Thanks very much.
> Lis
>|||Hi Bruce - Thanks for the quick reply. I tried scheduling a report
that actually pulls from a SQL Server database and though the
subscription ran just 30 minutes ago, Report Manager still took over a
minute to open... Thanks for the info on refreshing the report.
Unfortunately, that's not really a viable option because I'm trying to
get this to work for a remote client. I don't want anyone there to
have to have anything open on their desktop all day.
Any other suggestions?
Lis|||Other than to tell you that it shouldn't take so long to open Report
Manager. I assume that if you open report manager, close IE, open up IE and
Report Manager the second time it is fast?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<info@.techknowsolve.com> wrote in message
news:1168555000.446295.230260@.o58g2000hsb.googlegroups.com...
> Hi Bruce - Thanks for the quick reply. I tried scheduling a report
> that actually pulls from a SQL Server database and though the
> subscription ran just 30 minutes ago, Report Manager still took over a
> minute to open... Thanks for the info on refreshing the report.
> Unfortunately, that's not really a viable option because I'm trying to
> get this to work for a remote client. I don't want anyone there to
> have to have anything open on their desktop all day.
> Any other suggestions?
> Lis
>|||Yes, it is fast the second time. Here's another thing: yesterday I
read that I could change the idle timeout setting so that it never
times out by removing the check in the box that says "shutdown worker
processes after being idle for (time in minutes):" I did that, but
I'm still having the same problem.
:(
Lis