Your going to regret changing the timeout-- your will hose up your server with ASP.NET queues building... I am telling you, your missing an index in your database. Have you tested the Query through the analyzer? Is it doing table scans where you should have an index? Have you run the Index Wizard?
As for SQLConnectionTimeout- that isn't a property of anything.... As I said already- your problem is, most likely, IIS being tired of waiting for the page to process so it aborts it.
The connection timeout itself is part of the SQL Connection String that your using-- However, you need to extend the ASP.NET page timeout also.
Google can help you with the exact syntax.
Hal Levy
I am here to help you, not do it for you.
That is, unless you hire me. I am looking for work.
|