Joan OBryan (2/8/2010)
The easiest way I found to recover in this scenario was to take the database OFFLINE (not detach!) and then bring it back ONLINE in Enterprise Manager. This worked very well in SQL Server 2000 and didn't affect any of the other databases in the instance. I haven't encountered this kind of suspect db in SQL Server 2005 yet.
Not always it would work. I had a database suspect just 10 - 12 days back and I tried to change the status to 24 (recommended in most sql sites)
SET Status = 24
WHERE [Name] = 'MyDatabaseName'
It did not work. Then tried offline and online method and it also did not work. with recovery method had no luck. Last option I had and did was to copy and paste data and log files on a different path and then drop suspected database. And then attached copied files giving new database name and then mapped all users and logins.
It worked like a charm.
I agree with most of the comments but there is no hard code rule guaranteed for getting suspected database online. It depends what ever method works for you.
Manager and users just want their database and they give a damn about how DBA gets it back,
By the way, its sql server 2000 sp4. Yeah, we still had some running on 2000.