I've got a DB that had a problem restoring, and now it's status is showing (Loading). I'm unable to detach it, delete it, or do anything with it. If I delete it from Enterprise Manager then do a refresh, it shows back up again.
Is there a way to positively, absolutely nuke this database?I've had a similar issue on a cluster instance once, however I was able to drop the database. As you might know the information about the databases available on the instance is present in the master database, so if all else fails (and it appears so) you might need to restore the master database, and then try to delete the problem database.
May I suggest doing this procedure at a time when there are little or no activity on the server, and of course that you back up the master database on right before you do the restore.|||when a restore truly hangs in the mangler, I script a restore explicitly specifying WITH RECOVERY and that usually completes the restore. then I would drop the db.|||True, but that would work if the database is presented as (restoring) right? Or will it work when it says (loading) as well?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment