Solution for long runnig reports

Question

Hi All!
I have a couple of long running reports. It can't be published on web, becouse brouser have short time out.
Can any body give me something like pattern for such case. I mean way to organize asinc communication with Reports server.
Mike

Answer 1

Depending on the type of report and how often the data needs to be refreshed, you could run the report at night and store the result in cache.
Another option is to take a look at your data model. Do you have a lot of queries and/or a lot of formula/summary columns? Things like these can, of course, slow things down. Try to rewrite your code if at all possible to do as many of the calculations in the SQL statement.
Now, this other option works very well for a lot of my larger reports even though Oracle strongly discourages it. A lot of times, I'll have some complex report that I'll write a stored procedure do get the data, do whatever needs done to it, and finally insert it into a temp table. The only drawback is that sometimes the after report trigger for whatever reason will get goofed up and not run the statement to delete that data. However, this is easy to take care of. Just set up a job in Enterprise Manager to periodically (at night) truncate the temp tables you're using.