Comments on: SQL SERVER – Quickest Way to – Kill All Threads – Kill All User Session – Kill All Processes

By: SQL SERVER – Weekly Series – Memory Lane – #015 « SQL Server Journey with SQL Authority

Sat, 09 Feb 2013 01:30:36 +0000

[...] Quickest Way to – Kill All Threads – Kill All User Session – Kill All Processes More than a year ago, I wrote how to kill all the processes running in SQL Server. Just a day ago, I found the quickest way to kill the processes of SQL Server. While searching online I found very similar methods to my previous method everywhere. Today in this article, I will write the quickest way to achieve the same goal. [...]

By: Rajdeep

Rajdeep — Thu, 25 Oct 2012 10:45:01 +0000

Hey Pinal,

Your syntax for killing users was Mind blowing, I had tried this shortcut, Its damn good, Thanks so much.

By: jagannath patro

jagannath patro — Tue, 07 Aug 2012 07:58:21 +0000

i want to kill a session for a particular user after 30 minutes of his login to be done automatically. i.e connection should be timed out after 30 minutes of his login time. how to do it?

By: Ken

Ken — Tue, 22 May 2012 19:20:37 +0000

Cool!!! This saves us a lot of time and keep going for this kind of examples.

By: Paul

Paul — Thu, 17 May 2012 18:54:02 +0000

Great article, i hope you keep posting these great examples.

By: mouna

mouna — Mon, 28 Nov 2011 10:49:38 +0000

Mouna.

Hi pinal,
can u help me, i want kill a restore process
i try to kill all process but i always get this message :
ALTER DATABASE is not permitted while a database is in the Restoring state.

By: Behnam

Behnam — Thu, 24 Nov 2011 04:46:13 +0000

you are the best ;-)

By: Jack

Jack — Tue, 15 Nov 2011 20:16:14 +0000

@Nagavara

Uh.. A bit of ‘that depends’ question, don’t you think? You are asking someone who has no knowledge of your system at all. Do some testing on a test server to find the answer yourself.

By: Nagavara

Nagavara — Wed, 09 Nov 2011 15:14:30 +0000

How long does the query execution takes place when i issue this script??

By: Ravi Pahuja

Ravi Pahuja — Tue, 26 Jul 2011 23:55:30 +0000

Hi Pinal,

Thanks for sharing this.

Really helpful.

Kind Regards,
Ravi Pahuja

By: Chris

Chris — Fri, 04 Mar 2011 13:49:30 +0000

Pinalkumar Dave you consistently provide the best solutions – Keep It Up. Everytime I see ‘sqlauthority’ from in google’s result I know I have the answer!

By: kernel_panic

kernel_panic — Sun, 15 Aug 2010 10:14:26 +0000

Hi Pinal,

Please bear with me, Im new to databases. I would just like to ask if are there any impact on the database/system after running your code?

Thanks in advance.

kernel_panic

By: Marko Parkkola

Marko Parkkola — Thu, 11 Mar 2010 13:37:15 +0000

I would have you publicly flogged for that ;) Just becuase there’s an easy way in C# to avoid situations like that:

using (var connection = new SqlConnection(@”c-s”))
{
var transaction = connection.BeginTransaction();
var command = new SqlCommant(@”sql-text”, connection, transaction);
command.ExecuteNonQuery();
} /* Connection will be closed and disposed here even if
you forgot to commit/rollback the transaction or
even when you forgot to close it explicitly */

By: Harminder Singh

Harminder Singh — Thu, 11 Mar 2010 11:46:14 +0000

If we start transaction from c# and forget to rollback this tran from c# then it lock table so your code will work in this scenario also.

By: Jerry Hung

Jerry Hung — Tue, 24 Feb 2009 20:41:05 +0000

Ha, I am scary to ever do this but it’s clever

don’t know where I got this, but another way to KILL all processes quickly (note: you’ll get errors because one cannot system processed)

DECLARE @SQL VARCHAR(8000)

SELECT @SQL = COALESCE(@SQL, ”) + ‘Kill ‘ + CAST(spid AS VARCHAR(10)) + ‘; ‘
FROM sys.sysprocesses
–WHERE DBID = DB_ID(‘X’)

PRINT @SQL
–EXEC(@SQL)

By: PP

PP — Sun, 08 Feb 2009 20:04:15 +0000

Good one…