GilaMonster (3/25/2013)
You won't be able to drop or restore the database, just restart SQL. Shouldn't take any recovery time at all.
I think that's the first time I've ever seen you give the advice to just restart the server to fix the issue--is this sort of thing a known problem in SQL Server?