C# - MSSQL Random Timeouts

added by mistralol

8/31/2011 9:01:19 AM

148 Views

If you have ever come across a c# application or any asp.net application for that matter that appears to work perfectly then without warning starts to fail with database timeout issues. There is one of two things normally wrong. Either it is a database problem. Or another rather common problem is actually in the code inside the application. This is when the developers and the database guys normally start screaming at each other. This normally happens because the developers cannot reproduce any problems in their enviroment and the dba's know that there database is in perfect working order and see little or no load on the sql server. This can happen if you have the following code

Read the full story

3 comments

dpeterson

8/31/2011 9:02:25 AM

I think this has less to do with SQL, and more to do with understanding exception handling in .Net better.
No code in your try block will run after the point at which the exception occurred, and putting cleanup code outside the try/catch will not work either as that code may not be reached if the exception handling throws the exception up the call stack. What needs to be used here is a finally statement, which will run whether an exception is thrown or not.

vijayst

8/31/2011 10:27:56 AM

It is interesting to read your article. I am curious to know how the maximum connections in the connection pool is configured. Thanks.

mistralol

9/1/2011 12:12:39 PM

Its in the connection string ...

string Args = "Data Source=SQL;Initial Catalog=Mess;Integrated Security=True;Connect Timeout=10;Timeout=10;Max Pool Size=10;"