![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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. |
#3
| |||
| |||
|
|
rdraider (rdraider (AT) sbcglobal (DOT) 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 (AT) sommarskog (DOT) se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/pro...ads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinf...ons/books.mspx |
#4
| |||
| |||
|
|
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. |
![]() |
| Thread Tools | |
| Display Modes | |
| |