Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Recovering database marked Suspect\Offline

Author  Topic 

Bob Knapton
Starting Member

1 Post

Posted - 2002-08-30 : 04:48:02
Hi,

We have an ongoing problem with our Win2K server - it periodically freezes and there is no way to 'thaw' it except by powering the system off. Normally this occurs out of business hours so there isn't a problem, but today I have ended up with a torn page in one of my SQL2000 databases and so I need to repair it.

I think that I can repair the database using DBCC CheckDB but the database is currently offline (the node in enterprise manager is marked as Suspect\Offline). I have tried every method I can think of to bring it online (EM, sp_dboption, ALTER DATABASE) but everything I try just stops the SQL 2000 service.

Interestingly, if I try to use DATABASEPROPERTYEX to test any status of any DB on the system it always returns NULL, but I don't know if this is significant or not. I do have a bad feeling about it though ;-).

People on other user groups have suggested a few things (thanks again if you're reading) but they haven't worked. I can't do a log backup because the person who set up the database used the simple recovery model. I've tried resetting the suspect status using sp_resetstatus but that returns a message saying that the staus is already correctly set.

If anybody has any ideas at all I'd be grateful to hear them.

Cheers,

Bob.

KnooKie
Aged Yak Warrior

623 Posts

Posted - 2002-08-30 : 06:49:31
You may have tried this already but my 2 cents....

//If your have a database that is marked suspect but there is no real
//problem this script will change the status flag and allow you to use
//the database. If you have more than one suspect database, comment
//the shutdown database section until you have changed the status on
//all suspect databases.

use master
go
sp_configure "allow updates", 1
reconfigure with override
go
update sysdatabases
set status = status - 256
where name = "database name"
and status & 256 = 256
go
sp_configure "allow updates", 0
reconfigure
go
checkpoint
go
shutdown
go

Paul
Go to Top of Page
   

- Advertisement -