SQL Server weirdness

[Rick Strahl [MVP]]

I have repeatedly run into the following problem while working on ASP.Net
applications and wonder if anybody else has seen this and might have an idea
for the cause:

While working on and debugging ASP.Net applications every once in a while
SQL Server will stall out and appear to lock up or become very, very slow.
ASP.Net connections try to connect but fail after the connection timeout.
Shutting down the debugged application, SQL Server and IIS does not fix this
problem. Interestingly enough though I can still connect and run queries
through Query Analyzer, but through .Net everything continues to time out.

Only a reboot seems to fix the issue. Other (non .Net) applications also
have problems with really slow connections, but they do work.

What could possibly cause this behavior, especially if everything that I can
think of has been shut down and restarted (AsP.net, IIS, SQL Server, the IIS
worker process)?


Any ideas?

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/wwHelp

 

[Cristian Suazo]

Do you have many connections open when get this problem? Do you have
connection pooling activated?

 

[Rick Strahl [MVP]]

I'm never sure when it really starts. But as I mentioned it continues even
if I shut SQL Server down, as well as IIS and VS.

I checked connection in PerfMon too a while back and the numbers are as
would be expected (ie. 1 open in Query Analyzer usually, 1 or 2 open for the
app). I typically open and close connections for all database operations
letting the SQL Connection pool do its thing. According to PerfMon there are
never more than 3-4 connections open and the connection limit is 10.

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/wwHelp