Comments on: SQL SERVER – Cursor to Kill All Process in Database

By: SQL SERVER - Quickest Way to - Kill All Threads - Kill All User Session - Kill All Processes Journey to SQL Authority with Pinal Dave

Sun, 08 Feb 2009 11:23:30 +0000

[...] Read here for older method of using cursor – SQL SERVER – Cursor to Kill All Process in Database. [...]

By: Ted A

Ted A — Wed, 19 Mar 2008 20:52:59 +0000

Follow up to my previous comment. It looks like the ” were removed. My apologies to Viren since I believe he did the same thing.

By: Ted A

Ted A — Wed, 19 Mar 2008 20:51:47 +0000

Outstanding thread. This was really helpful in building a process for our system. I really enjoyed the feedback with the multiple solutions.

Viren, the select statement is invalid.

I believe it should read..

select * from master.dbo.sysprocesses
where DB_NAME(dbid) = ‘Lutheran’
and spid > 50 and spid @@SPID

Thanks all.

By: John

John — Wed, 23 Jan 2008 21:44:50 +0000

I never use cursors for loops. Just prefer to stay away from them. Here’s my solution:

create proc msp_killallspids (@db varchar(255))as
declare @min int, @max int
declare @dbname varchar(255), @dbid int
declare @cmd varchar(255)

select @dbid = dbid from master..sysdatabases
where name = @db

select @min = min(spid) from master..sysprocesses where dbid = @dbid
select @max = max(spid) from master..sysprocesses where dbid = @dbid

while @min @min
end

By: viren

viren — Thu, 06 Dec 2007 19:04:06 +0000

Let me try again

”
select @@spid
DECLARE @sql VARCHAR(500)
SET @sql = ”
SELECT @sql = @sql + ‘ KILL ‘ + CAST(spid AS VARCHAR(4)) + ‘ ‘
FROM master.dbo.sysprocesses
WHERE DB_NAME(dbid) = ‘Lutheran’
AND spid > 50 AND spid @@SPID
select @sql
EXEC(@sql)

“

By: Benjamin

Benjamin — Wed, 29 Aug 2007 16:05:30 +0000

It helped!

Thanx!

By: Siddharth

Siddharth — Mon, 06 Aug 2007 10:21:29 +0000

Nice article it help me alot

By: fastian

fastian — Wed, 11 Jul 2007 09:04:34 +0000

For SQL server 2005:

CREATE TABLE #TmpWho
(spid INT, ecid INT, status VARCHAR(150), loginame VARCHAR(150),
hostname VARCHAR(150), blk INT, dbname VARCHAR(150), cmd VARCHAR(150), request_id INT)

request_id INT was missing…

By: Nandkishor

Nandkishor — Sun, 27 May 2007 08:49:55 +0000

There is no need to create the cursor to kill all the process on the sql server.
Instead we call compose a string like this

declare @SQLString varchar(8000)
set @SQLString = ‘Kill 51;Kill 52;kill 53′
exec (@SQLString)

which eleminate the need for cursor.

But we should check that the lengh of the string should be less than 8000.

that we can afford comared to Cursor.

Enjoy SQL

By: pinaldave

pinaldave — Fri, 18 May 2007 15:51:24 +0000

Thanks Ruslan your suggestion is implemented.
Regards,
Pinal Dave
(http://www.SQLAuthority.com)

By: Ruslan

Ruslan — Fri, 18 May 2007 15:29:15 +0000

–is not valid code
BEGIN
SET @tString = ‘KILL ‘ + @spid
EXEC(@tString)
FETCH NEXT FROM @getspid INTO @spid
END

– change
BEGIN
SET @tString = ‘KILL ‘ + Cast(@spid as varchar)
EXEC(@tString)
FETCH NEXT FROM @getspid INTO @spid
END