We recently deployed MR 2012 with CU6. Its only been about 3 weeks and the SQL Log files have reached 20 GB. What is the best approach to keep this down so it doesn't occupy the server space? Should I set the database to "Simple" recovery model?
*This post is locked for comments
I'd stay away from simple. What are you doing for backups? Any backup solution you use should be able to truncate SQL log files, and if it can't, look else where. At the very least, create a scheduled SQL job that runs a full backup at some point, then backs up the transaction log at various points during the day. After you've run your transaction log backups, shrink your log file to an appropriate size and you should be fine.
That's exactly what i would do. Just make sure your backups are done nightly as the logs will grow during the day but will truncate and release space after the backup is run. In my opinion you will never ever use a Transactional Log to restore from. But that is just my opinion.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (