Home/ Questions/Q 3981214
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T05:23:00+00:00

This sutiation can be easily reproduced on your test environment. Open SSMS and connect

  • 0

This sutiation can be easily reproduced on your test environment. Open SSMS and connect to you server. Open New Query tab connected to MYTEST database (I assume that MYTEST is online).
Don’t do anything with this tab. Open new tab connected to the same database. Type the following code in your new tab

USE master
GO
ALTER DATABASE MYTEST
SET OFFLINE

Your code will be head blocked by the process you are running from your first tab.(Please see Activity Monitor).
Why is the execution blocked even though there is no task accosiated with process in the first tab?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You’d need to tell SQL to kick every connection out

    ALTER DATABASE MYTEST
SET OFFLINE
WITH ROLLBACK IMMEDIATE

    This is by design: a connection to a database has shared DB lock, whether executing or not.

    WITH <termination>::=

    Specifies when to roll back incomplete transactions when the database is transitioned from one state to another. If the termination clause is omitted, the ALTER DATABASE statement waits indefinitely if there is any lock on the database. Only one termination clause can be specified, and it follows the SET clauses.

    Just run sp_lock (or whatever the new dmvs are 🙂 and you’ll see them

    • 0