October 30, 2014 at 1:41 pm
Had some issue with the connection and luckily I was running the trace. This happened 60 times, in 10 minutes. Can someone tell me what this sp_reset_connection is, how can I fix this issue?
"He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]
October 31, 2014 at 11:47 am
I am still hoping to get some answers from somebody who has experienced and dealt with these kinds of issue before.....
"He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]
October 31, 2014 at 12:13 pm
That is nothing to worry about, it's just your application performing some kind of connection pooling. See this article about common things you will see in a trace:
http://www.sqlteam.com/article/examining-sql-server-trace-files
In connection pooling, .Net will keep the same physical connection open, and will reset it whenever the application makes a new logical connection to the database through an existing physical connection:
http://msdn.microsoft.com/en-us/library/8xx3tyca(v=vs.110).aspx
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply