I have a ASP.NET App that is causing a bunch of sleeping process in
SQLserver. It sometimes causes the application to stop responding.

I've made sure that ll connections are being closed along with all
datareaders. Is there anything else that would cause a connection to stay
open?

Thanks,
AMerrell

I had this problem a while back. It's quite annoying!

I believe the reason was that connection pooling is on by default. If I
remember correctly, you can turn it off by adding 'Pooling=false;' to your
sql connection string (but you may want to check the SDK to be sure).

Hope it helps...


"AMerrell" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I have a ASP.NET App that is causing a bunch of sleeping process in
> SQLserver. It sometimes causes the application to stop responding.
>
> I've made sure that ll connections are being closed along with all
> datareaders. Is there anything else that would cause a connection to stay
> open?
>
> Thanks,
> AMerrell
>
>

Yes, closing the connection does not destroy it by default as connection
pooling happens by default. Closing it just returns it to the pool.

HTH,

--
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com

"niceguy" <(E-Mail Removed)> wrote in message
news:IUCVa.40600$(E-Mail Removed)...
> I had this problem a while back. It's quite annoying!
>
> I believe the reason was that connection pooling is on by default. If I
> remember correctly, you can turn it off by adding 'Pooling=false;' to your
> sql connection string (but you may want to check the SDK to be sure).
>
> Hope it helps...
>
>
> "AMerrell" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > I have a ASP.NET App that is causing a bunch of sleeping process in
> > SQLserver. It sometimes causes the application to stop responding.
> >
> > I've made sure that ll connections are being closed along with all
> > datareaders. Is there anything else that would cause a connection to
stay
> > open?
> >
> > Thanks,
> > AMerrell
> >
> >
>
>