COM+ Connection Pooling Doesn't Appear to be working on SQL Server 2005 Cluster

Question

We have a COM+ Data Layer that utilized Connection Pooling. Its deployed to 3 clusters, 2 SQL Server 2000 and 1 SQL Server 2005 environment.

We noticed today that our monitoring software is reporting Thousands of Logins per minute on the SQL Server 2005 box. I did some tracing in both environments and profiler is reporting this for the 2000 boxes:

sp_reset_connection
SQL CALL
sp_reset_connection
SQL CALL
sp_reset_connection
SQL CALL

and this for the 2005 box:

Audit Logout
sp_reset_connection
Audit Login
SQL CALL
Audit Logout
sp_reset_connection
Audit Login
SQL CALL
Audit Logout
sp_reset_connection
Audit Login
SQL CALL

Is there some sort configuration for SQL Server 2005 different from SQL Server 2000 that we might be missing that would be creating this issue?

Answer 1

No response after 4 months, but its no longer a concern for me.