Re: ASP.NET App Causing Sleeping Process in SQL Server by Greg
Greg
Thu Jul 31 08:07:42 CDT 2003
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" <nice.guy@ihatespam.com> wrote in message
news:IUCVa.40600$F92.4357@afrodite.telenet-ops.be...
> 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" <amerrell@harlingen.tstc.edu> wrote in message
> news:u0vxgEiVDHA.2004@TK2MSFTNGP11.phx.gbl...
> > 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
> >
> >
>
>