April 13, 2010 at 11:41 am
How about this approach?
Before Conversion:
A. take final transaction log backup
B. execute CHECKPOINT
C. Set simple recovery mode
D. take pre-conversion Full Backup
After the conversion I know we must resume full recovery mode AND take a full backup before incremental ( transaction log ) backups can resume.
April 13, 2010 at 11:57 am
Looks OK, though I'm not sure that you need the CHECKPOINT, or if you do need it, that it shouldn't be first instead of second (hopefully Paul or someone else will correct me if I'm wrong :-D).
Did you have any more specific questions about this?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
April 13, 2010 at 12:03 pm
No. Setting simple recovery before the full backup just lets me get to bed earlier as someone else is handling the backup. I just wanted to make sure the full backup captured everything in case it's needed for a rollback on Sunday.
April 13, 2010 at 2:36 pm
I don't think the checkpoint is needed. Once you switch to simple mode, a checkpoint will get run and until the full is run, you might be stuck.
Note that once you restore, or go back to full, I think you need a full before you can take log backups.
April 13, 2010 at 2:48 pm
Affirmative on having to take a full backup after resuming Full Recovery Mode in order to resume transaction log backups -- verified that through testing.
I need to read more about checkpoint. We did a large "split" project a few months back using the "alter table BigTable drop constraint YADA with (move to NewFileGroupOnMountPoint) Even in simple recovery we issued a checkpoint after each command to avoid filling up a 100GB transaction log. Seemed to help at the time.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply