Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Simple recovery model and logging.

Status
Not open for further replies.

TheBugSlayer

Programmer
Sep 22, 2002
887
US
Guys,
one the databases I was recently asked to administer has its recovery model set to simple. In EM, on the General tab of the DB properties, it states that the last database backup took place on 6/21/2004 3:18:46 AM (this morning, it runs daily) and the last transaction log backup took place on 5/1/2004 3:44:48 AM.

That leads to the following questions:
1- Why is there any last log backup if the simple recovery model is set to SIMPLE? Is it possible that it used to be otherwise and was later changed to SIMPLE?
2- What is the most up-to-date copy of the database I can recover in case of failure/disaster? The last database backup only?
3- Normally, in case of failure, I would backup the current log, apply the previous ones and then recover with this one, up to the point of failure or whatever the case might be, is there any similar possibility here?
4- I am planning on changing the model to FULL, any implications? Can you give me some guidelines.

Thanks.
 
1 - That would be my guess or someone performed a manual backup.

2 - You could recover to 6/21 3:18am.

3 - I'm not sure I follow you here. Since you don't have a ldf backup you can't restore it. If you were to back it up right now, you could restore your mdf then ldf to recover to right now. You're testing my memory, but I think that's right.

4 - Make sure your trans log doesn't run out of space. Regular/frequent backups should occur to ensure the trans log is regulary truncated.

hth

-If it ain't broke, break it and make it better.
 
How critical is the data? Most databases don't need to be recovered up to the minute - usually only those with user interaction where the users can't re-input. It's much simpler to leave it as simple with full and diff backups.

1. Yes
2. Yes
3. no
4. as above - include differential backups



======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top