This simple script (ran from the master database) in Query Analyser removes all the requirements of collating currently connected spids to a database and the need to systematically open a cursor to kill each spid individually by simply placing the database offline, then immediately online.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

2 (1)

You rated this post out of 5. Change rating

2007-03-16 (first published: 2007-02-13)

368 reads

Discuss

All authors

Blogs

Query multiple Azure SQL Databases

By hellosqlkitty

I was sick of changing context in Azure Data Studio while cleaning up things...

KDA: Echoes of Deception - Case 3

By Zikato

The crime spree in Digitown is not ending. This time 20 cars have been...

The Book of Redgate: Do Your Best Work

By Steve Jones

One of our mission statements in the Book of Redgate says: attempt to do...

Read the latest Blogs

Question of the Day

In SQL Server, when the buffer manager write pages to disk, page protection is added to the pages. There are two types of protection: torn page protection and checksum page protection. What happens with regards to concurrency with page protection during writes?

See possible answers

Database File Summary

Find The Database Recovery Model

Easily Kill All Users In A Database

Blogs

Query multiple Azure SQL Databases

KDA: Echoes of Deception - Case 3

The Book of Redgate: Do Your Best Work

Forums

Shining a Light on Shadow AI - Responsible Data Protection When AI is Everywhere

CAST(VARCHAR(n)) resolved performance issue?

isnull, coalesce overhead

Question of the Day

The Internals of Writing a Page