Re: Regarding Suspect Database
From: Noorali Issani (naissani_at_softhome.net)
Date: 03/23/04
- Next message: Saul: "RE: MMC - Application Error"
- Previous message: Deepali Ananth [MS]: "RE: MMC - Application Error"
- In reply to: Noorali Issani: "Re: Regarding Suspect Database"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 23 Mar 2004 16:15:52 +0500
Hari,
After doing all the steps which you told but still the status of the
database is Suspect - Emergency Mode, what should I do ? Can you tell me
about
Update sysdatabases set status = 32768 where name = "BadDbName"
Can you tell me that 32768 ( it represting what) , is there any other table
from where I can get the whole detail of this status, u getting me what I
wanna say ?
Thanks Hari,
"Noorali Issani" <naissani@softhome.net> wrote in message
news:u56RGi$DEHA.2052@TK2MSFTNGP11.phx.gbl...
> Thanks alot Hari
>
> "Hari Prasad" <hari_prasad_k@hotmail.com> wrote in message
> news:OUvqBX$DEHA.3716@TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > Use emergency mode (also called bypass mode) to recover data when SQL
> Server
> > marks a database suspect and the automatic recovery will fail.
> >
> >
> > 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
> >
> > Reconfigure with override
> >
> > GO
> >
> > Update sysdatabases set status = 32768 where name = "BadDbName"
> >
> > Sp_configure "allow updates", 0
> >
> > 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,
> >
> >
> > Thanks
> > Hari
> > MCDBA
> >
> > "Noorali Issani" <naissani@softhome.net> wrote in message
> > news:e0F5Wr8DEHA.2052@TK2MSFTNGP11.phx.gbl...
> > > Hari , One question here... can you please explain this..
> > >
> > > 2. Start the database in Emergency mode , Update the Status column in
> > > master..sysdatabases table for that database to 32768.
> > >
> > >
> > > Thanks
> > > Noor
> > >
> > > "Noorali Issani" <naissani@softhome.net> wrote in message
> > > news:%23DqkBf8DEHA.3804@TK2MSFTNGP09.phx.gbl...
> > > > Thanks Hari...
> > > >
> > > > Regards
> > > > "Hari" <hari_prasad_k@hotmail.com> wrote in message
> > > > news:uhke752DEHA.3696@TK2MSFTNGP10.phx.gbl...
> > > > > Hi,
> > > > >
> > > > > There are various possibilities for a Suspect status
> > > > >
> > > > > 1. The MDF or LDF file for the database is not available during
> > startup
> > > > > 2. LDF file missing or Corrupted
> > > > > 3. MDF file page allocation problems.
> > > > >
> > > > > 1. The first one can be resolved by executing "sp_resetstatus"
> stored
> > > > > procedure and restart SQL server services
> > > > > 2. Start the database in Emergency mode , Update the Status column
> in
> > > > > master..sysdatabases table for that database to 32768.
> > > > > After this database will be usable with out transaction log.
> AFter
> > > this
> > > > > create a new database and use DTS to transfer objects and data.
> > > > >
> > > > > 3. Third one is critical , try executing DBCC CHECKDB with
> > > REPAIR_REBUILD
> > > > > option. If the problem is not rectified
> > > > > wither restore from Backup or contact Microsoft support.
> > > > >
> > > > > Thanks
> > > > > Hari
> > > > > MCDBA
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "Noor" <anonymous@discussions.microsoft.com> wrote in message
> > > > > news:3CAC7A08-1F9A-433A-83E3-CE5DD8A597FC@microsoft.com...
> > > > > > Can any body let me know about the suspect database what is the
> > > remedies
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
- Next message: Saul: "RE: MMC - Application Error"
- Previous message: Deepali Ananth [MS]: "RE: MMC - Application Error"
- In reply to: Noorali Issani: "Re: Regarding Suspect Database"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
