How to detect orphaned connections?

Question

0.00/5 (No votes)

See more:

SQL-Server-2005

, +

Over a year ago I've asked similar question on forums, but no one answered.

I use sp_who and sp-who2 procedures for querying processes, but I can't figure out how to effectively detect orphaned connections/processes.
You will agree that LastBatch information should be ignored in most cases.

I would like to make job or service for logging some statistical data about server usage.

Posted 14-Apr-11 3:14am

Oshtri Deka

Add a Solution

2 solutions

Solution 1

Do you mean from the sql side of things or the application side? You gotta be a lot more specific. And what do you mean by "orphaned" connections? As far as a .Net application goes, you should ALWAYS close a connection after using it. There are few reasons to keep a database connection open for the life of a given application.

Posted 14-Apr-11 3:23am

#realJSOP

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dylan Morley · Accepted Answer · 2011-04-14T03:59:00

Solution 2

I think orphaned connections are allocated a negative SPID, you can grab them from syslockinfo (master db) like...

SQL

select * FROM syslockinfo WHERE req_spid=-2

Here's an article on the subject

http://www.sqlserverclub.com/articles/how-to-deal-with-negative-spids-in-sql-server.aspx[^]

Google for req_spid=-2 and you'll get a few hits on the subject

Posted 14-Apr-11 3:59am

Dylan Morley

Comments

Oshtri Deka 14-Apr-11 15:08pm

I'll check it out tomorrow.