Timeline for SQL Server DROP Database which is in a long roll back process
Current License: CC BY-SA 3.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 13, 2018 at 23:11 | history | edited | CommunityBot |
replaced http://sqlblog.com/blogs/adam_machanic/archive/2011/04/27/who-is-active-v11-00-a-month-of-activity-monitoring-part-27-of-30.aspx with http://whoisactive.com
|
|
Jan 8, 2015 at 11:19 | comment | added | OverflowStack | OK thank you :-) I hoped that there is a way around waiting. As it is currently still rolling back.. | |
Jan 8, 2015 at 11:04 | comment | added | Kin Shah |
you can not kill a SPID that is doing a rollback .. Thats why I mentioned that you can check the status of rollback using kill spid with statusonly . You have to wait for the rollback to finish.
|
|
Jan 8, 2015 at 10:50 | comment | added | OverflowStack | you can not kill a SPID that is doing a rollback.. :( for perfect understandable reasons that this would make your DB inconsistent. However in this case I dont care and want to even fully drop my DB! :-) | |
Jan 8, 2015 at 10:47 | comment | added | Kin Shah | my point was to find out what SPID is locking the database exclusively. Kill that SPID, so you can drop the database. | |
Jan 8, 2015 at 10:19 | comment | added | OverflowStack | Altering of the Database does not work because it cannot be locked. | |
Jan 8, 2015 at 10:14 | history | answered | Kin Shah | CC BY-SA 3.0 |