creating cached-instances of the report for each possible

Question

creating cached-instances of the report for each possible

Valued Member

Points: 64

June 1, 2005 at 11:00 am

I have a report that takes quite some time to render.So I would like to create cached-instances of the report for each possible variable value.I suppose this is a rather common problem. Is there a solution (script, program) available somwhere to do this?(I've tried some things with the scripts but I can't get it to work, I keep geeting "timed out' errors (although de report execution is set not to time out) or security exeptions (althoug my user is a RS system user with all the authoroty))Thank you

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Todd Harness Old Hand Points: 363 More actions · Answer 1

I am not sure why you are timing out but you could try a couple of other ways.

1 way would be to create filters and pull the full data set. That would allow you to cache one report and then let the users filter what they want to see. Although if you having time out problems this may not work.

Another solution would be to create a linked report in the report manager and specify the different parameters for each copy of the linked report. That way you only have 1 rdl to manage and maintain.

Good luck

Antoon Vansina Valued Member Points: 64 More actions · Answer 2

These parameters are not query-parameters, but filter-parameters. But rendering from a snapshot still takes a lot of time (it is a lot of data and a complex report).

Linked reports is ok but won't let me navigate to other parameter-values

Todd Harness Old Hand Points: 363 More actions · Answer 3

I know that turning the parameters into query parameters would take a lot of development time to redo the report especially when it is a complex report, however doing so would reduce the amount of data retrieved and would shorten your refresh time. Would that be an option?

Antoon Vansina Valued Member Points: 64 More actions · Answer 4

Not really, I could solve it all by creating special tabeles that allow for fast access. But the appeal of RS was the possibility to cache these reports, and not to work with live data

Todd Harness Old Hand Points: 363 More actions · Answer 5

my only other suggestion would be to talk to your dba (if that is not you) to check the default query timeout settings on your server to see if that could be modifed to enable your query to run long enough to finish.