Database connection pooling

[Chris Smith]

Can someone tell me why setting "Connection Reset=false" in the database
connection string seems to makes connection pooling work in .NET 2. I need
the value to be 'true' so that the connection is cleaned up before being
used again.

My application (an ASP.NET web app running on Win Server 2003 and using
impersonation) opens separate SqlConnection instances to a SQL Server (SQL
7), executes a stored procedure on each connection and then closes the
connection. At any one time then only one connection is open.

Each connection is opened with exactly the same connection string as below.
If I set "Connection Reset=true" then in Performance Monitor I still see
HardConnectsPerSecond increasing each time that the connection is opened. If
I just set the value to false and restart the application then the
HardConnectsPerSecond value doesn't constantly increase each time that a
database connection is opened.

The connection string is:
Initial Catalog=MyDatabase; Data Source=MyServer; Connect Timeout=30;
integrated security=SSPI;persist security info=False;Trusted_Connection=Yes;
Application Name=MyApplication; Pooling=true; Connection Reset=true; Min
Pool Size=5