up vote 1 down vote favorite
share [g+] share [fb]

I've got an application where all the sprocs are running nice and quick, but the sp_reset_connection calls between them are taking anything up to 20 seconds. I've looked at locking and blocking but can't see any happening and don't understand how this would effect sp_reset_connection. Help!

link|improve this question
1  
Are you just now seeing this behavior or has it "always" been there? This link doesn't help anser your question but provides a nice list of what happens when the proc runs..sqldev.net/articles/sp_reset_connection/default.html – jl. Nov 9 '10 at 17:54
Is it causing a problem? – gbn Nov 9 '10 at 18:02
It's causing a big problem since I'm using connection pool and the next time ado.net uses the connection it sites there and waits for this to complete. – Andrew Hancox Nov 10 '10 at 9:37
feedback

1 Answer

up vote 1 down vote accepted

I've figured out what the issue was. It looks like when you run a trace the data gets written as part of this sproc, this means that if you're tracing into a table and the insert speed isn't stellar everything grinds to a halt.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.