Re: best recovery mode

From: Hari Prasad (hari_prasad_k_at_hotmail.com)
Date: 06/25/04 

Date: Fri, 25 Jun 2004 21:57:52 +0530

Hi,

We can not differentiate and tell which one is good and which one is bad,
Recover model selection purely depends
on the data inside the database and type of recovery business requires.

FULL :- For production data which requires point-in-time recovery

BULK_LOGGED :- For production with high bulk operations and which do not
need a point-in-time recovery

SIMPLE :- For test and development environments. The recovery can be done
only till the last full backup.

Have a look into "Selecting a Recovery Model" in Books online for more
details.

Thanks
Hari
MCDBA

"reddy" <reddy@discussions.microsoft.com> wrote in message
news:E42CF3FF-F4EC-476C-AFC0-D81428240791@microsoft.com...
> hi friends,
>
> what should be the best recovery mode to implement.it is
simple,full,bulklogback.
> which should be the efficient .
> what is the microsoft recommendations for this
>
> please help
>
> thanks
> reddy

Relevant Pages

  • Re: NTDS ISAM DataBase Corruption
    ... Did you tried the recover the corrupted Active Directory process that a gave ... This is brand new IBM Server. ... using symantec livestate recovery. ... Active Directory database is unavailable because it is damaged, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Crash recovery after shutdown immediate?
    ... database stated it wanted a recovery. ... it seems that a crash recovery occured. ... ARCH: Archiving is disabled ... After that, I did a backup, NOT a restore. ...
    (comp.databases.oracle.server)
  • RE: Eseutil and restored database - Jet database errors
    ... database repair (hard recovery). ... It approximately spends 1 hour for 6~8 GB database. ... Please refer to the "Method 3: Restore a Mailbox from Backup to a Recovery ...
    (microsoft.public.exchange.admin)
  • Re: Recover mailbox from old Backup...
    ... I never want to use these database files as a production mailstore. ... run the eseutil check, create a Recovery Store Group, ... I still have all the files from the old Exchange 2003 folder ... > I am running Exchange Server 2003 and the database files are from Exchange ...
    (microsoft.public.exchange.admin)
  • Re: [Info-Ingres] W_DM5061_WRONG_BLOB_LENGTH in verifydb
    ... database and the recovery has simply reproduced this, ... Subject: W_DM5061_WRONG_BLOB_LENGTH in verifydb ... writefailed with operating system error 0 ...
    (comp.databases.ingres)