sql server reporting services: I am having trouble rendering reports through the ReportingService.Render
method which take longer than the 120 second default IIS connection timeout.
Is there a solution other than increasing the IIS connection timeout? Of
course I am using the infamous PDF rendering extension, attempting to create
a financial report for one year's worth of data so these reports easily take
over 2 minutes.

Have you considered?

1. Snapshot reports
2. Subscribed report delivery to a file share
3. Aggregating the report data and offloading it to a report database/table
assuming that you are trying to report off an OLTP database.
4. Truncating a few quarters worth of data :-) You users may never find out
that you are off a few millions...
--
Hope this helps.

-----------------------------------------------------
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
-----------------------------------------------------

[quoted text, click to view]

I don't think you have to modify the IIS connection timeout (i.e.globally
change anything). This can be on a dataset by dataset basis. I frequently
set the timeout much less for datasets I know should return quickly. Click
on the ... and modify it. I haven't had anything that took longer than 120
seconds so I don't know what happens if you increase this. Could be that you
would still come up against the IIS connection timeout. Give it a try.

Another issue that would definitely work is to schedule it. If it runs as a
scheduled job then the IIS timeout won't affect it at all. I guess it
depends if you can have default parameters or not (remember they can be an
expression).

Bruce L-C

[quoted text, click to view]