adragon218
asked on
sql server suspect
after reboot server , a database in sql server 6.5 suspect. we try to turn it to emergency mode to made it available again . But we still can't access the database.
And in the event log ,error logged as follow:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) could
not be found. It contains the following insertion string(s): Error : 605,
Severity: 21, State: 1, Attempt to fetch logical page 1160 in database
'RERS_WS' belongs to object '1490104349', not to object 'ItemCategory'..
Any method to repair the database so we can access it again?
As I known , we can use 'bcp' program to
copy out the data from the database ,
how to use this command?
And in the event log ,error logged as follow:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) could
not be found. It contains the following insertion string(s): Error : 605,
Severity: 21, State: 1, Attempt to fetch logical page 1160 in database
'RERS_WS' belongs to object '1490104349', not to object 'ItemCategory'..
Any method to repair the database so we can access it again?
As I known , we can use 'bcp' program to
copy out the data from the database ,
how to use this command?
ASKER
we have tried to change it to emergency mode , but it still not work ,
we want to know how to change to normal state to recover the database
we want to know how to change to normal state to recover the database
Because the database has been marked suspect, its status must be reset. To do this, perform the following steps:
Use the supplemental stored procedure sp_resetstatus to reset the status of a suspect database. If you have not already done so, create this procedure by executing the Instsupl.sql script, found in the Mssql\Install directory. For more information on sp_resetstatus, see the "Resetting the Suspect Status" topic in the SQL Server Books Online.
Execute sp_resetstatus in the master database for the suspect database:
use master
go
sp_resetstatus <db_name>
Stop and restart SQL Server.
Verify that the database was recovered and is available.
Run DBCC NEWALLOC, DBCC TEXTALL, and DBCC CHECKDB.
This might help.....we have had a suspect database before and the reset seem to work...hope u can recover ur database...good luck
Use the supplemental stored procedure sp_resetstatus to reset the status of a suspect database. If you have not already done so, create this procedure by executing the Instsupl.sql script, found in the Mssql\Install directory. For more information on sp_resetstatus, see the "Resetting the Suspect Status" topic in the SQL Server Books Online.
Execute sp_resetstatus in the master database for the suspect database:
use master
go
sp_resetstatus <db_name>
Stop and restart SQL Server.
Verify that the database was recovered and is available.
Run DBCC NEWALLOC, DBCC TEXTALL, and DBCC CHECKDB.
This might help.....we have had a suspect database before and the reset seem to work...hope u can recover ur database...good luck
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
http://www.ntfaq.com/ntfaq/sql29.html#sql29