Chances are your pool won't run out of connections but it's possible that if
you're
blowing out of the program without closing the connection you could have so
many connections open that SQL Express runs low on memory and slows down
enough so connection time out. It could also be that you're single stepping
through logic so it's taking an unnaturally long time for operations to
complete so they time out. I sometime bump up the timeouts in the
connections string if I'm going to be debugging.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Marina Levit [MVP]" <ma*****@comcast.netwrote in message
news:pd******************************@comcast.com. ..
If the pool is out of connections, you will get a message telling you
this.
If it is just a timeout, it is something else. I've also never had an
issue with the IDE holding on to connections even if I forgot to close
them. When I stop debugging my executable, that process finishes, and any
connections it may have open are closed and those resources released.
"Earl" <br******@newsgroups.nospamwrote in message
news:OB*************@TK2MSFTNGP03.phx.gbl...
>After I run the debugger awhile on the same app (change, run, change,
run, etc. ad nauseaum), I start getting timeout errors on connection. I'm
speculating that the connection pool is being used up at some point. I am
taking the obvious step of making sure connections are closed after they
are used, so I'm wondering if the garbage collector or the IDE is keeping
connections alive although I've closed them? Any way to check the number
of available connections or the "pool" count? Anything peculiar about
SQLExpress that might be causing this (I've always used SQL2000 in the
past and this is the first time I've seen a timeout issue)?
