Microsoft SQL

A while back, I wrote an article for SQL Server Central, describing a neat way for Microsoft SQL DBA’s to clear out connections / SPIDs to a database without breaking much of a sweat. Although I love SSC, I just can’t get past the fact that they require a visitor to register in order to view full articles. So, here it is, a reproduction of the DB script and a rather good explanation on how to use it or apply it. This goes out to all my fellow MSSQL DBAs in peril out there.

This script opens a little cursor that will clean out connections to any DBs you specify. It will release SPIDs that are active on a DB or which are locking a related SPID. I found the base script some time ago -I wish I remembered the author or location- but I’ve modified it ever so slightly to provide for a good package that can be used prior to starting a DB restore for example.

Feel free to play with it and adapt it to whatever needs you may have. I’ve used this, at times, to kill SPIDs which were causing blocking conditions. You should be able to easily modify it to go after very specific conditions. You can also packaga this up into a nice stored procedure and be able to call it programmatically in times of need.

DECLARE @dbspid as int
DECLARE @dbname as varchar(50)
DECLARE @killcommand as varchar(50)

–SET @dbname = ‘db1′

DECLARE ConnectionKiller CURSOR FOR
SELECT sysproc.spid FROM sysprocesses AS sysproc
INNER JOIN sysdatabases AS sysdb ON
sysdb.dbid = sysproc.dbid
WHERE sysdb.NAME IN (@dbname)
AND sysproc.spid <> 0
UNION
SELECT sysproc.blocked FROM sysprocesses AS sysproc
INNER JOIN sysdatabases AS sysdb ON
sysdb.dbid = sysproc.dbid
WHERE sysdb.NAME IN (@dbname)
AND sysproc.blocked<>0

OPEN ConnectionKiller

FETCH NEXT FROM ConnectionKiller INTO @dbspid
WHILE @@FETCH_STATUS = 0
BEGIN
SET @killcommand = ‘KILL ‘+CAST(@dbspid AS VARCHAR(50))
EXEC (@killcommand)
FETCH NEXT FROM ConnectionKiller INTO @dbspid
END
CLOSE ConnectionKiller
DEALLOCATE ConnectionKiller

Share on Facebook