How can I kill bad sessions without rebooting or stopping SQL?

Posted on 2008-06-11
Last Modified: 2010-08-05
I have a client running a program using SQL2005. They are getting sporadic error msgs that the software vendor is actively working on. In the meantime they are getting these errors which cause users to be kicked out of the program. Problem is, they cannot log back into the program because the database still thinks they are in. The only way the client can get these users back in is to restart SQL or reboot the server. This is a major inconvienience for the other 15 or so users who are working in the program. Is there a utility which allows him to see active connections to the database and kill them??
Question by:wdabbs
  • 4
  • 2
  • 2
  • +1

Expert Comment

ID: 21760651

If you suspect orphaned processes exist on your SQL Server, the following are steps you can take to troubleshoot the problem:
1.      Identify the orphaned processes using sp_who, which may tell you which applications were associated with these processes through the host names.
2.      After you identify these orphaned processes, you may choose to either ignore them if they are not holding any locks or using many connections, or kill them using the SQL Server KILL command.
3.      Check with the application users for any improper procedures of closing applications, such as warm or cold restart of workstations without exiting the applications first. Check whether there is any history of the workstation becoming unstable, such as a general protection fault, and so forth. Correct those improper procedures or stability problems if they do exist.
4.      Check whether the IPC session is still active on the Windows NT Server computer where SQL Server is running. Depending on the IPCs you are using, the commands are different. For example, if you are using named pipes, the command is "NET SESSION" or "NET FILES"; if it is a TCP/IP sockets connection, you can use "NETSTAT" to display active TCP sessions; in case of IPX/SPX, you may have to use the Performance Monitor to monitor the "Connections Open" for "NWLink SPX."
5.      If the IPC sessions are still active on the Windows NT Server computer, it is perfectly normal for SQL Server to keep those connection processes. When Windows NT clears up the IPC sessions, SQL Server will be notified and clear up the connection processes accordingly. You may be able to adjust certain Windows NT network parameters to shorten the time period that Windows NT has to wait before clearing up the dead sessions.
LVL 60

Expert Comment

ID: 21760671
select * From sys.dm_exec_connections
where session_id > 50

find the processes you want to kill and pass them to the KILL statement


Author Comment

ID: 21761238
once I identify the process ID by running select * From sys.dm_exec_connections
where session_id > 50 against the database.. How do I then "pass them to the KILL statement?

Author Comment

ID: 21761400
Also.. When I tested this, by logging into the database myself, I see that 12 session were created when I logged in. This is not what I had expected. Do I need to kill all 12 sessions? And does this undo any work done??
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

LVL 60

Expert Comment

ID: 21761883
If they are inside a transaction then it will be rolled back.

Also, you only create one connection (only one is possible) when you log into the server.

YOu can use this procedure to do it also...just when you load the temp table, make sure you set criteria on the processes you want to kill...
create procedure usp_KillDBProcesses(

	@dbname as varchar(20)




DECLARE @strSQL nvarchar(255)

DECLARE @spid varchar(10)

DECLARE @dbname2 varchar(40)

CREATE table #tmpProcesses


	spid int,

	eid int,

	status varchar(30),

	loginname varchar(50),

	hostname varchar(50),

	blk int,

	dbname varchar(50),

	cmd varchar(30)



--check to see who is currently in the databases


SELECT spid, dbname FROM #tmpProcesses 

WHERE dbname = @dbname

--load cursor for values from table (processes)

OPEN LoginCursor

FETCH NEXT FROM LoginCursor INTO @spid

WHILE (@@fetch_status <> -1)


	IF (@@fetch_status <> -2)


		--kill processes

		SET @strSQL = 'KILL ' + @spid

		EXEC (@strSQL)


	FETCH NEXT FROM LoginCursor INTO @spid


CLOSE LoginCursor


DROP table #tmpProcesses



Open in new window

LVL 51

Accepted Solution

Mark Wills earned 500 total points
ID: 21761991
You can also use the SQL Server Management Studio...

In object explorer, go down to management, then activity monitor, and the Activity Monitor screen will display. on the right hand side, you can right click on a process and "kill Process". You can see who and what it is doing, so is a bit more interactive. And yes, it is process by process... You can apply filters to help with the "noise"
LVL 60

Expert Comment

ID: 21762013
Management Studio...yuck.  
LVL 51

Expert Comment

by:Mark Wills
ID: 21762057
Techo :D
LVL 60

Expert Comment

ID: 21762903 said you wanted to pass the connections to a kill statement...which is what my solution did.

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Read about achieving the basic levels of HRIS security in the workplace.
Never store passwords in plain text or just their hash: it seems a no-brainier, but there are still plenty of people doing that. I present the why and how on this subject, offering my own real life solution that you can implement right away, bringin…
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

896 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now