R
Rob Kraft
I have an application that makes hundreds of database calls in the first few
seconds it loads up. During this time, it opens 100+ connections. ALL of
the connections use the exact same connection string. Connection pooling is
turned on. This is a VStudio 2005 C# ADO.Net 2.0 .Net 2.0 application. It
uses default settings against SQL Server 2005. Is my app so fast that the
connections don't get re-used? Also, ALL of the connections are opened
inside a USING statement, and dispose always gets called.
I guess I am trying to determine how ADO.Net decides to open a new
connection in the pool versus re-using an existing sleeping connection.
seconds it loads up. During this time, it opens 100+ connections. ALL of
the connections use the exact same connection string. Connection pooling is
turned on. This is a VStudio 2005 C# ADO.Net 2.0 .Net 2.0 application. It
uses default settings against SQL Server 2005. Is my app so fast that the
connections don't get re-used? Also, ALL of the connections are opened
inside a USING statement, and dispose always gets called.
I guess I am trying to determine how ADO.Net decides to open a new
connection in the pool versus re-using an existing sleeping connection.