July 29, 2014 at 12:01 pm
A .Net 4.0 Web application uses both SQLNCL10 and ODBC to connect to a SQL Server 2008 R2 Standard Edition database server. Every now and then the application experiences quite a few "Query timeout expired" exceptions. The frequency doesn't follow a pattern and doesn't have a specific period. Sometimes the app reports the problem for an hour on specific portions of the app and sometimes the duration of the problem is longer. The pages in the Web app that experience the issue have a lot of SQL calls and open and close quite a few connections, but on a normal day, those pages work just fine without reporting any kind of problem. In addition, those same pages are some of the most used parts of the system as well. We have already vetted the app servers, and they didn't have any CPU or Memory issues at the time of the events. The SQL jobs that were running at the time of the events do not take a long time to complete, except a DBCC job for consistency check of tables which is a new introduction and takes up to 9+ hours to complete. That being said, we do not experience the time outs every time this job is run either.
Based on my research so far, the problem can originate from lack of memory on the database server, uncommitted transactions, locks, or long running queries.
However, with such limited amount of information, there is very little to use to try to pin point the problem. How would I go about debugging and solving this issue?
July 29, 2014 at 2:56 pm
When you have a situation like this, there are a lot of places that have tools that will automatically run through all the diagnostic information for you.
One of my favorite places is http://www.brentozar.com/first-aid/downloads/. sp_AskBrent is a good place to start.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply