Timeout question re. strongly typed datasets and objectdatasources

Question

I have now found a TON of crappy not clear, not relevant examples of ways I can start to tackle the problem. Can't believe i've spent any more than 10 minutes on this but it's been 3 hours so far.

I am looking at an aspx page with next to no code behind. This page renders a crystal report out to a pdf.

The crystal report is bound to an objectdatasource which is bound to one of the tableadapters in a stupidly large dataset.

The problem is the query times out. It's a long running proc, (50 seconds) and timeout is 30 seconds. I have looked at adding a partial class but since the objects are not bound in code i wouldn't be able to set the timeout that way and it's a web site and as such the code behind for the dataset is a whole bunch of XML anyway and i'm not sure I can add a partial class here to expose the time out and if I could i'd be repeating about 70 times, once per adapter.

So does anyone have a better, simpler or at least a method that works so I can get this crystal report, today :)

Thanks

Answer 1

Can't you increase the ConnectionTimeout of the SQLCOnnection used to fill the dataset?

i.e. SQlConnection.ConnectionTimeout = somevalue

Answer 2

There are two possibilities: Optimize the procedure or increase your connection timeout.

I know you said it's the command timing out, but I'd bet that it's the connection to the database that is timing out. I've never heard of the command object timing out.

Have you tried changing/setting the time out in the connection string?

Answer 3

If you can't modify the TableAdapter's timeout, and assuming the procedure can't run any quicker, then i don't see any option other than to set the report's data source to the stored procedure directly. Crystal doesn't really care about timeouts that low.