This is not about changing the ASP code but app pool max settings on your website application/connection pooling.

query timeout can be effected by the "query wait (s)" setting of the sql sever... to set it to endless value run the script below.

sp_configure 'show advanced options', 1
reconfigure

sp_configure 'query wait (s)', -1
reconfigure

sp_configure 'show advanced options', 0
reconfigure




      

I can't see anywhere in the application settings to change the pool settings.

Tigin44: What other effects will this change have?

you should run the above scripts against the server

What other effects will running that script have on my application?

its probably that "query wait (s)" running value is set to -1 meaning queirws will run till they complete...
you can check the detailed information from books online about sp_configure......

Connection Pooling for the .NET Framework Data Provider for SQL Server
http://msdn.microsoft.com/en-us/library/8xx3tyca(VS.71).aspx

Using Connection Pooling with SQL Server
http://msdn.microsoft.com/en-us/library/8xx3tyca(VS.80).aspx

you set the values in your config files/connection string for the Max Pool Size

or maybe you were hit by the bug below:
http://support.microsoft.com/kb/948868/en-us

or maybe you only need to close your data reader before close connection

>>What other effects will running that script have on my application? <<
It will have no effect on your application.  A timeout is a client setting and has nothing to do with the server.

I would debate that as by letting the query to wait indefinitely could seriously impact the server and implicitly the APP (sorry to say it) on poorly written SQL code. Please see note below from Microsoft and consider twice before changing it. I would rather decrease it instead of making unlimited and if you have a APP performance issues there are many other ways to detect/deal with it.

http://msdn.microsoft.com/en-us/library/ms189539.aspx

"A transaction that contains the waiting query may hold locks while the query waits for memory. In rare situations, it is possible for an undetectable deadlock to occur. Decreasing the query wait time lowers the probability of such deadlocks. Eventually, a waiting query will be terminated and the transaction locks released. However, increasing the maximum wait time may increase the amount of time for the query to be terminated. Changes to this option are not recommended."

 

lcohan: As I mentioned, I cannot make any changes to the application code, but I will look at the hotfix issue you describe

It looks like Windows Server 2008 R2 has that hotfix included in it.

That's what I was afraid of. I'll keep this thread open for another day or so and see if there are any other ideas, and the I'll close it.

I have a ticket in with the vendor. They have acknowldeged the problem and are working on it.