|
| PORTAIL | ANNUAIRE | ARTICLES | COMPARATEUR HÉBERGEURS | DEVIS | FORUMS | RÉDUCTEUR D'URL |
|
|
|
|
||||||
 |
|
|
LinkBack | Outils de la discussion |
20/09/2007, 19h02
|
#1 |
Messages: n/a
Hébergeur: |
Delete or detach a Suspect database
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. Thanks. |
|
|
20/09/2007, 23h25
|
#2 |
|
Messages: n/a
Hébergeur: |
Re: Delete or detach a Suspect database
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/pro...ads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinf...ons/books.mspx |
|
|
|
21/09/2007, 03h22
|
#3 |
|
Messages: n/a
Hébergeur: |
Re: Delete or detach a Suspect database
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/pro...ads/books.mspx > Books Online for SQL Server 2000 at > http://www.microsoft.com/sql/prodinf...ons/books.mspx |
|
|
|
21/09/2007, 09h14
|
#4 |
|
Messages: n/a
Hébergeur: |
Re: Delete or detach a Suspect database
rdraider (rdraider@sbcglobal.net) writes:
> 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. The last thing you should believe is a graphical tool. But they usually offer a Refresh option to handle such situations. -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.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 |
|
|
|
| Outils de la discussion | |
|
|
