Recover SQL Database from suspect status

Hi I'm trying to recover database from a suspect status but when I run this
command:
sp_resetstatus webc
sql return me this message:
Prior to updating sysdatabases entry for database 'webc', mode = 0 and
status = 1073741840 (status suspect_bit = 0).
No row in sysdatabases was updated because mode and status are already
correctly reset. No error and no changes made.
What is it= What can I do to recover DB?
Thanks.
--
Filippo Macchi
Hi
> No row in sysdatabases was updated because mode and status are already
> correctly reset. No error and no changes made.
Have you tried to restart SQL Server? Aren't you still available to see your
data?
It seems you have to set your database in emergency mode
update sysdatabases set status=32768 where name='your name'
"Azkaban" <azkaban74@.libero.it> wrote in message
news:uZL0MLWQEHA.556@.tk2msftngp13.phx.gbl...
> Hi I'm trying to recover database from a suspect status but when I run
this
> command:
> sp_resetstatus webc
> sql return me this message:
> Prior to updating sysdatabases entry for database 'webc', mode = 0 and
> status = 1073741840 (status suspect_bit = 0).
> No row in sysdatabases was updated because mode and status are already
> correctly reset. No error and no changes made.
> What is it= What can I do to recover DB?
> Thanks.
> --
> --
> Filippo Macchi
>
|||Hi,
Stop and start the SQL server and try accessing the webc database
use webc
go
select * from sysobjects
If it still gives the error then go thru the below informations:-
Details:-
Suspect database may be due to below reasons.
1. MDF or LDF files may be used during the SQL Server service startup
2. LDF file might be corrupt or immediate power shutdown caused the LDF to
corrupt
3. MDF file - Page allocations issue
For the point 1.
Just Run sp_resetstatus <dbname> and restart SQL server (This you have done
already)
For the point 2. ( LDF file might be corrupt or immediate power shutdown
caused the LDF to corrupt)
a. Start SQL Server in emergency mode
Setting the database status to emergency mode tells SQL Server to skip
automatic recovery and lets you access the data.
To get your data, use this script:
Sp_configure "allow updates", 1
go
Reconfigure with override
GO
Update sysdatabases set status = 32768 where name = 'webc'
go
Sp_configure "allow updates", 0
go
Reconfigure with override
GO
You might be able to use bulk copy program (bcp), simple SELECT commands, or
use DTS to extract
your data while the database is in emergency mode.
After this database will be usable with out transaction log. AFter this
create a new database and use DTS to transfer objects and data
For point 3. Very critical error , try executing DBCC CHECKDB with
REPAIR_REBUILD option. If the problem is not rectified try
with restore from Backup or contact Microsoft support.
Thanks
Hari
MCDBA
"Azkaban" <azkaban74@.libero.it> wrote in message
news:uZL0MLWQEHA.556@.tk2msftngp13.phx.gbl...
> Hi I'm trying to recover database from a suspect status but when I run
this
> command:
> sp_resetstatus webc
> sql return me this message:
> Prior to updating sysdatabases entry for database 'webc', mode = 0 and
> status = 1073741840 (status suspect_bit = 0).
> No row in sysdatabases was updated because mode and status are already
> correctly reset. No error and no changes made.
> What is it= What can I do to recover DB?
> Thanks.
> --
> --
> Filippo Macchi
>
|||I run the command and received this message, is it correct?:
Server: Msg 259, Level 16, State 2, Line 1
Ad hoc updates to system catalogs are not enabled. The system administrator
must reconfigure SQL Server to allow this.
"Uri Dimant" <urid@.iscar.co.il> ha scritto nel messaggio
news:uWWEfRWQEHA.3660@.tk2msftngp13.phx.gbl...
> Hi
> Have you tried to restart SQL Server? Aren't you still available to see
your
> data?
> It seems you have to set your database in emergency mode
> update sysdatabases set status=32768 where name='your name'
>
> "Azkaban" <azkaban74@.libero.it> wrote in message
> news:uZL0MLWQEHA.556@.tk2msftngp13.phx.gbl...
> this
>
|||Hi
Sp_configure "allow updates", 1
go
Reconfigure with override
go
Update sysdatabases set status = 32768 where name = 'yourname'
go
Sp_configure "allow updates", 0
go
Reconfigure with override
go
"Azkaban" <azkaban74@.libero.it> wrote in message
news:uyJxIXWQEHA.904@.TK2MSFTNGP12.phx.gbl...
> I run the command and received this message, is it correct?:
> Server: Msg 259, Level 16, State 2, Line 1
> Ad hoc updates to system catalogs are not enabled. The system
administrator
> must reconfigure SQL Server to allow this.
>
> "Uri Dimant" <urid@.iscar.co.il> ha scritto nel messaggio
> news:uWWEfRWQEHA.3660@.tk2msftngp13.phx.gbl...
> your
>
|||Hi,
Can you go thru the steps specified by me in the previous post. That
contains the detailed information on recovering from the suspect status.
Thanks
Hari
MCDBA
"Azkaban" <azkaban74@.libero.it> wrote in message
news:uyJxIXWQEHA.904@.TK2MSFTNGP12.phx.gbl...
> I run the command and received this message, is it correct?:
> Server: Msg 259, Level 16, State 2, Line 1
> Ad hoc updates to system catalogs are not enabled. The system
administrator
> must reconfigure SQL Server to allow this.
>
> "Uri Dimant" <urid@.iscar.co.il> ha scritto nel messaggio
> news:uWWEfRWQEHA.3660@.tk2msftngp13.phx.gbl...
> your
>