SQL Server Command Timeouts Timeout expired. The timeout period elapsed prior to completion of the o
- by user104295
Hi there, we've had a ASP.NET web application deployed for a number of years now.... last week we migrated to a slightly slower server to save some money.
Now we're frequently getting command timeouts:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding
This is understandable in that a slower server will take longer to produce results; take longer time and produce a timeout.
Is there any system-wide way to get SqlClient to set a longer timeout? We cannot change the code, as it's everywhere... we're using multiple data access technologies as well.
Maybe there's a default command timeout setting on a connection string? We just need to increase it by 30 seconds; we're happy to wait a bit longer for queries to return.
thanks