I have inherited a suite of .Net c# applications from a developer which talk to an Informix database on a unix server. 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. Connection pooling is turned via the ODBC administrator. Is there any way of seeing how many ODBC connections are open? What is the effect of turning off connection pooling? Am I right in thinking the .NET framework will use connection pooling anyway?