I have several databases that I'd like to move over to FULL recovery mode so we can have point-in-time restore capability. We don't need it on all of our databases, just the ones that are transaction heavy and contain data that is constantly being updated.
I've done lots of research and I fully understand what happens when you switch over to FULL recovery, especially how it pertains to the log file.
What I'm looking for is some suggestions or 'gotchas' that may arise from switching some to the FULL recovery model.
Right now, I plan on doing one database at a time, so I can monitor log file growth and determine the best frequency for log file backups to ensure we don't get into a runaway log file situation. I'm also aware that as soon as we switch to FULL recovery that I need to run a full backup on that database. (I understand that FULL mode won't be truly enabled until we do this).
My plan is also to weekly run a full backup, wipe the log files from the previous week and, essentially 'start over'.
Are there any other considerations or advice that would be helpful. Anything I should watch out for? We run full index rebuilds, DBCC CHECKDB and statistics rebuild once a week too. Are there any potential problems with those operations (maybe switch to BULK_LOGGED for that time period as to not explode the log file?)
Thanks for all your help!