Connection Pooling

• Stephen Fletche

  SSC Enthusiast

  Points: 103

  More actions

  November 28, 2007 at 2:59 am

  #119579

  I've been looking at connection pooling (because I had a connection leak) and largely understand the principal.

  However, I've come across this (below) in some code...

  ConnectionState originalConnSt = dbConnection.State;

  try

  {

  do stuff, including opening the connection if it's not open

  }

  finally

  {

  if(originalConnSt == ConnectionState.Closed)

  { dbConnection.Close() }

  }

  Everything I read says ALWAYS close the connection when you've finished using it. This returns it to the pool.

  I guess what was trying to be achieved here was leaving the connection open between calls.

  Is this actually any more efficient than opening and closing the connection each time, given that it would be taken from the pool anyway?

  Thanks for any advice.

• Kishore.P

  SSCrazy Eights

  Points: 8147

  More actions

  November 28, 2007 at 3:10 am

  #754890

  use using(...) {....}, for more information see MSDN.