Yesterday i ran the "SQL Server Profiler" tool and outputted the data to a table, now when i look in it i find many "exec sp_reset_connection" rows and thats expected with our data access layer!
But what i can't explain is that some times it takes 8 seconds to execute this query…
What could cause the sp_reset_connection to delay that much?
Best Answer
You sure it is 8 seconds?
Starting with SQL Server 2005 (as stated in BOL)
when a trace is saved to either a file or a database table, the duration column value is in microsecondsUpdate
Came across this post on SO: sp_reset_connection taking a long time to run