ADO.NET manages connection pooling itself, If you do a close or dispose
it does'nt really mean that connection to db server is closed. When you call
connection.close or adapter.close, it actually closes connection to your
applications
object with ado.net, on the other hand ADO.NET is itself maintaining
connections
with database.
Its very important to close both data reader and connection as soon as they
are no longer needed. if you do not do this, they will go out of scope and
the
application will leak a connection and u'll see one more connection.
check this msdn documentation for reference:
http://msdn.microsoft.com/library/en...esigntools.asp
--
Hope this helps,
Zeeshan Mustafa, MCSD
"z. f." <zi**@info-scopeREMSPAM.co.il> wrote in message
news:OK**************@TK2MSFTNGP10.phx.gbl...
Hi,
i use asp.net and i have a general class that manages database access
using ado.net and sqlclient provider.
this class upon deconstructor closes connection to DB.
it appears on sql 2000 manager when i look in management/current
activity/Process Info that my connections stays open and the number of
connections open is increasing each request.
what am i missing / doing wrong here.
thanks for any input from your experience.
z.