Cant delete a database

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?

Can't connect to SQL Server 2005 Reporting Services

Hi all, for some reason I can't connect to SQL Server 2005 reporting services. When I try to log in I get "the request failed with HTTP status 404:Not Found".

When I installed SQL Server, port 80 was not available as I am also running Apache, so SQL Server Report Server runs at http://localhost:81/ReportServer/ .. this work fine, I have build a report, deployed it successfully and can view it.

In SSMS I see two 2 databases, ReportServer and ReportServerTempDB.

Everything looks OK in the Report Server Configuration Manager, however in the Surface Area Configuration when I click on "
Windows Integrated Security" under the Reporting Services node it also comes back as "the request failed with HTTP status 404:Not Found"

Does anyone have any ideas how I can fix this, does it look like it is looking for Reporting Services on the wrong port? 80 instead of 81 ?

Thanks for any advice

Hello, I have had a similar problem and posted a thread on it at: http://tinyurl.com/zke4g

I've been running IIS 5.1 on port 200 just for security as hackers go straight for 80 if they are trying anything. While my problem is similar to yours, I have seen nothing that says the port is the problem especially given it persists when I switch IIS to port 80. A common move with Apach is to go into the config file and set apache to :8080, I've done that though it's been years and the details of how to are fuzzy.

Good luck. - Greg