title: ODBC Connection Pooling
body: <p>I have inherited a suite of .Net c# applications from a developer which talk to an Informix database on a unix server.</p>
  
  <p>Instead of using the usual practices for managing the database connections (disposable pattern / "open late / close early"), the code seems to open one ODBC connection when each app loads and doesn't close it.</p>
  
  <p>Is there any way of seeing how many ODBC connections are open?</p>
  
  <p>I am trying to make a case for refactoring the code in the applications to use .NET best practices but I am meeting with resistance because the current code works. </p>