Change from Full to Simple Recovery, what to do with the Log file?

  • Kit G (11/3/2010)


    So, I do a full backup at 1:00pm on a Sunday. Each night, at 11:00pm, I have the Diffential backup scheduled to run.

    If the database won't change on the weekend, you'd probably do a full on Monday night, and diffs on Tue, Wed, Thu, Fri. If the database might change over the weekend, you might do diffs on Sat, and Sun. If you want to get tricky, you could check the t-log to see if there are entries since the last diff, but that's going to involve undocumented features, so I don't recommend it.

    On Tuesday, at 3:00pm, my database goes bellyup and I have to restore. So, the restore process would start at the full backup done on Sunday at 1:00pm, then add on the backup done Sunday night and Monday night, leaving me with whatever data changes were done between 11:00 Monday night and when the database went bellyup to deal with.

    Not quite. You'd use the Full and the most recent Diff, but you don't use any Diff except the most recent.

    But, instead of having to store three days of full backups, I would only be storing a full backup plus whatever changes were made each day? This would definitely make things a bit easier space-wise as the database isn't in use over the weekend.

    Precisely.

    ... By the way, I got the log file reduced in size. DBCC SQLPERF showed that 0.07% of the log file was in use (out of 105GB). It is now shrunk down to 15MG with 10% in use and I'll keep an eye on it to see how the usage goes.

    Awesome. That should work.

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • Well Kit, Gus just said everything I was going to... and since we both know he's always right... :w00t:;-)

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes


    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

  • WayneS (11/3/2010)


    Well Kit, Gus just said everything I was going to... and since we both know he's always right... :w00t:;-)

    heh. Probably best if I just nod wisely at this point. :hehe:

    -- Kit

  • WayneS (11/3/2010)


    Well Kit, Gus just said everything I was going to... and since we both know he's always right... :w00t:;-)

    You're the third person to accuse me of that.

    The first was me.

    The second was Phil Factor (from Simple-Talk).

    So it must be true! :w00t:

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • Kit G (11/3/2010)


    WayneS (11/3/2010)


    Well Kit, Gus just said everything I was going to... and since we both know he's always right... :w00t:;-)

    heh. Probably best if I just nod wisely at this point. :hehe:

    or sarcastically... 😀

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes


    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

Viewing 5 posts - 16 through 19 (of 19 total)

You must be logged in to reply to this topic. Login to reply