How can I capture queries that fail on the SQL Server due to connection drops/failures?

Question

Profiler doesnt seem to capture if there is a connectivity loss.

What is calling the query? Is it an SQL job or a bit of code? — twoleggedhorse, Dec 28 '12 at 14:46
A third party service on which I dont have much control/cannot change — Sam P, Dec 28 '12 at 18:50

score 0 · Answer 1 · edited Apr 13 '17 at 12:42

0

Without catching the exception in the code this is not the easiest thing to do.

Have you checked the error logs in SQL? DA has a related answer for doing this: https://dba.stackexchange.com/questions/10364/sql-server-error-log-monitoring
You can check that your profiler is set up correctly:
http://support.microsoft.com/kb/224587
There are a number of sql monitoring tools out there, just google 'SQL server monitoring'.

edited Apr 13 '17 at 12:42

Community

answered Dec 29 '12 at 14:36

twoleggedhorse

1. Error logs dont show which query failed due to network failure 2. That link doesnt talk much about profiling for network issues 3. There are just too many – Sam P Dec 31 '12 at 03:29
In that case try this: http://stackoverflow.com/questions/295299/sql-server-timeout-logging along with this article: http://www.sqlmag.com/article/sql-server-profiler/gathering-deadlock-information-with-deadlock-graph – twoleggedhorse Dec 31 '12 at 09:24

1 Answers1