Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Our production server is running SQL Server 2008 (non r2).

I'm working on investigating and issue that appears to be networking or connection related, where our web server is losing or dropping connections to the database server.

It would assist me greatly to have a method or counter that I can use to track DROPPED connections to the SQL Server. Specifically, we want to know if the ODBC/ADO connection was forcibly closed by the CLIENT.

Conceivably we could also track when a query was cancelled by the client, which may give us the same information.

From my own research I don't see a way to track this with perfmon counters, but I'm not that familiar with them.

share|improve this question
I take it you already know about the connectivity ring buffer? – Martin Smith Feb 18 '14 at 14:07
@MartinSmith You take it WRONG! I'll read about it, thanks. – JNK Feb 18 '14 at 14:08

To give information on the performance counter side...

The only performance counters I know of that might help would be the ODBC counters for disconnects. SQL Server has a counter for killed connections but those are connections killed by SQL Server, not the client.

You would have to capture these at the client which you could use typeperf command to do this remotely. SimpleTalk has a good article about using this command.

The comment suggestion would be the more human way of doing things.

share|improve this answer
Good info, thanks! – JNK Feb 18 '14 at 15:43

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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