Posted by rdraider on 09/21/07 01:22

No queries would work since this database did not exist in
Master.sysdatabases. Not sure why. Attempting to detach from Enterprise
Manager produced an error. Then I simply closed and reopened EM and it was
gone! Odd.



"Erland Sommarskog" <esquel@sommarskog.se> wrote in message
news:Xns99B1EF3C598D6Yazorman@127.0.0.1...
> rdraider (rdraider@sbcglobal.net) writes:
>> Everything I read about sp_resetstatus says you must restart SQL after.
>> Is there a way around that (don't want to shut down production). The
>> suspect db is just an empty db that is not needed. I need to create
>> another db with the same name.
>
> I may be missing something, but what about DROP DATABASE? I made a quick
> test on SQL 2000 where I created a database, stopped SQL Server, deleted
> the log file to make the database suspect, and restarted SQL Server.
> DROP DATABASE worked just fine.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Re: Using ASP.NET to login to SQL Server 2005 Database
• Prev in forum: Re: How Do I give EXECUTE Permissions on Stored Procedures?
• Thread view: Re: Delete or detach a Suspect database

[Reply to this message]