Re: Emergency Mode

From: Paulo Ferreira (anonymous_at_discussions.microsoft.com)
Date: 08/05/04 

Date: Thu, 5 Aug 2004 05:11:41 -0700

If you can access to data when on Emergency Mode, then
you may have one of the folowing:
1- the log file is corrupt, and this is the best news i
can give you at this point, simply put the database on
suspect mode again and rebuild the log (dbcc rebuild_log
('dbname','complete path to new log file')
2- you may have dirty pages on datafile, now that is bad
news, try creating a new db and export all objects and
data to the new database. You may have a lot of work to
check if all data has been exported, but at least you
have some data.

Now if you don't see any data when on emergency mode then
check the path to the mdf and if all the ndf (if any) is
correct. if it is.. sorry should have made backups.

you can also try the log explorer from Lumigent to data
on logs/data.

Best regards
Paulo ferreira

>-----Original Message-----
>Hi,
>
>Seems like your database MDF or LDF file was not
available during SQL server
>startup. This will make the database to Suspect status.
What you can do is:-
>
>execute the procedure
>
>sp_resetstatus <dbname>
>
>after that sto and start the MSSQL server service and
see the database
>status.
>
>If it still shows emergency mode then the LDf file might
be corrupted. So
>you can update the database to emergency mode and do a
DTS to copy the data
>and objects to a new database.
>
>Thanks
>Hari
>MCDBA
>
>
>
>"Nida Thiengthum" <kook@scic-ltd.com> wrote in message
>news:ep6Ij9seEHA.2532@TK2MSFTNGP09.phx.gbl...
>> My database 's marked suspect when I restart my
computer.
>> It's too bad I don't have backup. Then I try to make
database in
>> emergency mode and use DTS to tranfer table. I ready
see my database and
>> table and change it to Normal mode for backup but I
can't . It still
>> say can not backup, the database is in emergency
mode.Otherwise, I can't
>> connect the database by the application.How should I
do or I done
>> something wrong ?
>>
>> Thank you again.
>>
>> KooK
>>
>>
>> *** Sent via Developersdex
http://www.developersdex.com ***
>> Don't just participate in USENET...get rewarded for it!
>
>
>.
>

Relevant Pages

  • Transaction log problems
    ... just before you backup the ... database change the recovery model to ... Simple, shrink the log file then change it back to Full, ... >transaction log and it is causing us some problems. ...
    (microsoft.public.sqlserver.server)
  • Re: Unable to attach the database
    ... BUT NEVER DELETE A LOG FILE! ... If you have a clean backup of the database, ... good understanding of SQL Server and how to work from this situation. ...
    (comp.databases.ms-sqlserver)
  • Re: Stanby cannot be moved forward
    ... It very much looks like by opening the database you have switched the ... a log file. ... A backup is taken from production server to backup server. ...
    (comp.databases.oracle.server)
  • Re: does this backup sequence commit all data to the database
    ... The database is in FULL recovery mode. ... During the day you BACKUP the LOG to files. ... At night you TRUNCATE the log "to flush the log file of committed ...  Then you shrink the log file and backup the database. ...
    (comp.databases.ms-sqlserver)
  • RE: Log File for Database " " is full Problem
    ... I do a backup of the database, ... I then run dbcc sqlperf on the log file after the backup and it ... SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan ...
    (microsoft.public.sms.admin)