January 14, 2009 at 1:38 pm
Sorry about the wrong information. Default instance is running on port 1433 and named instance is running on dynamic port.
January 14, 2009 at 1:41 pm
The connection of the The App was killed !
You should start by verifying what was going on on the server at that time!
* Noel
January 14, 2009 at 1:51 pm
The message saying the connection was forcefully closed usually means that either the connection was explicitly killed by someone, or the query hit a high severity error and was disconnected.
Both of those will be reflected in the SQL error log. Check there.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 14, 2009 at 2:06 pm
How can i verify what is going on the server? I checked the error log, there is nothing there.
Should I turn on the profiler? What event should i capture in profiler?
January 14, 2009 at 2:58 pm
I set the profiler to audit fail login, login, sql:batchstarting, sql:batchcompleted.
Do i need to collect some other events?
January 14, 2009 at 11:55 pm
The error events. Exception, errorlog, user error message, attention. There may be some others worth checking.
How long are you planning running profiler for?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 15, 2009 at 8:39 am
I have set the profiler for error event.
I am planning to run profiler until erorr occurs again and application stops sending updates. Is that OK?
January 19, 2009 at 10:34 am
what event i have to start to collect information regarding network issues?
I hope this is not sql server isssues or port issue.
Viewing 8 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply