R
RickT
If I setup DB connections from a:
- client-activated remote object
- to use SQL Authentication
- individual SQL Server accounts (each user has their own SQL login ID &
password)
Assuming that the object stays instantiated, will the .net connection pool
keep the DB connection live (in the pool) even though a method within the
object executed a conn.Close()?
I'd like to have the application code practice good form and .Close whenever
the method finishes with the connection, without paying the performance
penalty of making & closing 3 db connections to execute 3 object methods by
the same user.
- client-activated remote object
- to use SQL Authentication
- individual SQL Server accounts (each user has their own SQL login ID &
password)
Assuming that the object stays instantiated, will the .net connection pool
keep the DB connection live (in the pool) even though a method within the
object executed a conn.Close()?
I'd like to have the application code practice good form and .Close whenever
the method finishes with the connection, without paying the performance
penalty of making & closing 3 db connections to execute 3 object methods by
the same user.