Reporting Services cache reports problem

We have a report that takes a very long time to run (no way to optimize) and the user cannot wait for it, so it must be cached.  My problem:  The data pull runs at :20 after, finishes at about :40.  The cache is flushed at say :50, but the cache takes a while to swap, say from :50 to :60.  Is there no way to trigger the swap after the cache is flushed?

Doesn't the user run the risk of opening the report and having to wait: (:45 - :60)  It doesn't make sense (for me) to have the cache flushed, then swapped.  Am I missing something?

FYI I use a subscription to swap the cache for 12 different parameter values (languages).  The reports display an unual amount of text, thus the length.

Any help appreciated,

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

How many parameters are on report. Is it just the language or are there 12 differnet parameter inputs?
billinbAuthor Commented:
There are four other parameters other than language in report, but they go to defaults.  The users don't care about the other four and know to export before changing them.   As example, one parameter is test section, multi-select, and the default is the entire dataset.  So there are 12 different parameter combinations stored in cache.

There is a data driven subscription that runs the 12 values for language, so there are 12 runs in cache.
The data driver table is just a one column list of the languageID's, i.e. 1033, 1036, 3084 etc.  So yes, there are 12 parameter inputs for language.  Does that answer your question?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
billinbAuthor Commented:
If anyone wants to take a stab at it, that would be fine.  I'd like to close this out pretty soon.

The question is fairly vague.  Basically I'm stuck with this huge report with huge text fields.  The user would have to wait a fairly long time, unless the report was cached.  The data updates throughout the day.  If there were 15 minutes out of each hour that the report wasn't cached, the users would hit on it frequently (Murphy's Law)

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.