Thanks for the replies.
I have another related question. If I still want to use cache (which will be
we don't want users to run the report for the current month. For example, if
executed and thus not cached. Is it possible?
"toolman" wrote:
> Keith,
> I think bb has the best idea with setting up subscriptions, thereby
> controlling when the report gets run.
> Other possible solutions are to
> use a snapshot instead of a cache, making the parameter value static
> or rewriting the proc so that while still dynamic, the parameter values
> are set programmatically
> or set your cache to expire every 24 hours so the data is current even
> though the first user every day gets stuck with the two minute wait.
>
>
> bb wrote:
> > couldnt you set up a subscription to request the report on the date and
> > time you want it generated?
> >
> >
> > something like this ...
> >
> >
http://msdn2.microsoft.com/en-us/library/ms155876.aspx > >
> >
> > db
> >
> > ----------------------------
> >
http://www.osix.net > > the geek programming challenges.
> >
> >
> > Keith wrote:
> >
> > > I've created a report (Regional Sales Report) using RS2000. The report
> > > has mutiple tables, charts and subreports and against a large database.
> > > It has two parameters: Year and Month. It takes about 2 minutes for a
> > > user to run the report online.
> > >
> > > So the performance is a critical issue here. On Report Manager, I set
> > > the Execution Property to "Cache". In this way, only the first user
> > > takes two minutes to run the report. Other users who run the same
> > > report for the same month will get the cached report very fast. This is
> > > exactly what I wanted - to cache the previous months reports once they
> > > are generated.
> > >
> > > But here lies the potential problem. Users are supposed to run the
> > > report on the first days of each month, for example, running the
> > > May-2006 report on 6/1/2006. But if someone runs the report for the
> > > current month, for example, June-2006, on 6/15/2006, then the report is
> > > generated and cached (data up to 6/15/2006). On 7/1/2006, when users
> > > run the report for June, they will get the cached report which only
> > > contains data to 6/15/2006, not the full month.
> > >
> > > Does anyone know how to solve the problem? Or have any other solutions?
> > >
> > > Any help is much appreciated.
> > >
> > > Thanks,
> > > Keith
>