Re: Help! What's with the open connection?
From: Wardeaux (wardeaux_at_bellsouth.net)
Date: 04/08/04
- Next message: DJM: "How to change a DataRow inside an event handler?"
- Previous message: Ron Fluegge: "ODBC Connection with SQL Managed Provider"
- In reply to: Raymond Lewallen: "Re: Help! What's with the open connection?"
- Next in thread: William \(Bill\) Vaughn: "Re: Help! What's with the open connection?"
- Reply: William \(Bill\) Vaughn: "Re: Help! What's with the open connection?"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 8 Apr 2004 17:37:10 -0400
Guys,
Thanks so much!! As you can tell I'm fairly new to the "inner bowels" of
SQL Server... I understand that "pooling" is a good thing for performance.
Here's my anxiety: I'm going to be having somewhere between 500 and 2000
simultaneous asp.net sessions using about 500 different SQL DBs... My
concern is this: what is going to happen if everytime I open a connection to
a DB, and I tell it to "Close" but it gets left open in a pool for 4-8
mins... will I be getting connection denials (too many open connections) or
is SQL smart enough to deal with this... or am I just getting paranoid with
my first solo commercial release?
Any help/reply is most appreciated!!!
thanks again!
wardeaux
"Raymond Lewallen" <Raymond.CTR.Lewallen@nospam.faa.gov> wrote in message
news:%23TAPPsPHEHA.3356@TK2MSFTNGP11.phx.gbl...
> Ah, I wasn't thinking. He's trying to delete an entire database, in which
> case my suggestion would not work with pooling enabled. Deleting objects
in
> the database would be fine at this point, but the pool still has the
> connection to the database. Wardeax, you might trying setting
pooling=false
> or the lifetime to nSeconds in your connection string to help you out
there.
> Might look up some info on connection pooling in the help.
>
> Sorry for the initial misinformation, and thanks to William for his
> correction to my post.
>
> Raymond Lewallen
>
> "William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message
> news:egTVzvOHEHA.2876@TK2MSFTNGP09.phx.gbl...
> > Yes, but unless you disable the pooler, the connection will be held for
> 4-8
> > minutes (as he was seeing).
> >
> > --
> > ____________________________________
> > William (Bill) Vaughn
> > Author, Mentor, Consultant
> > Microsoft MVP
> > www.betav.com
> > Please reply only to the newsgroup so that others can benefit.
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > __________________________________
> >
> > "Raymond Lewallen" <Raymond.CTR.Lewallen@nospam.faa.gov> wrote in
message
> > news:evtBfDOHEHA.3200@TK2MSFTNGP10.phx.gbl...
> > > Wardeaux,
> > >
> > > Use the Close or Dispose method of the connection object (oDBCon) to
> > release
> > > it back into the connection pool. Look up the SqlConnection.Close
> method
> > in
> > > your MSDN help library.
> > >
> > > Raymond Lewallen
> > >
> > >
> >
> >
>
>
- Next message: DJM: "How to change a DataRow inside an event handler?"
- Previous message: Ron Fluegge: "ODBC Connection with SQL Managed Provider"
- In reply to: Raymond Lewallen: "Re: Help! What's with the open connection?"
- Next in thread: William \(Bill\) Vaughn: "Re: Help! What's with the open connection?"
- Reply: William \(Bill\) Vaughn: "Re: Help! What's with the open connection?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|