Anand S (5/8/2009)
I am facing a similar problem in my project - I don't see the issue in development, but when we move to production the number of sleeping connections grow rapidly and sql server starts refusing new connections (the software is pretty useless at this stage).
You mention that after closing, sql server holds the connection for a period of time (1 min or so). Is there any documentation that gives this information and also any idea whether this number is tunable/Changeable ?
Yes, there is documentation. You need to check the specific one for you development language/environment. The connection pooling is on your application side and not on your DB side... In most languages you can turn connection pooling off...
(Maybe can be worth checking into your connection strings, that they are the same over the whole application. Constantly changing configuration strings makes connection pooling almost useless).
Not using a DAL approach might also negate the use of connection pooling...