0

I have numerous replication subscribers that have to have backups done to keep log files under control. They do get a LOT of inserts/deletes during the day. I have been using simple recovery because the data does not really need to be backed up.

I am switching to Ola’s very cool Maintenance Scripts because it is easier and faster to deploy and reindexing can be more selective.

With Ola’s Maintenance Scripts – Can anyone see a reason not to leave the recovery model simple? Or should I go with full and backup the logs to every hour to keep them small? This is just for replication subscribers.

  • Why doesn't your data need to be backed up? Also why would the use of a maintenance script affect your position on the importance of your data? – Erik Oct 29 '15 at 17:52
  • Agree with Erik. Short answer is No, but maybe you're trying to get at something else here? Are you doing hourly snapshots of subscribers or something? – Dave Oct 29 '15 at 18:53
  • The servers are replication subscribers. They have copies of the data that lives on the publisher. The data gets full backups there. – Mike M Oct 29 '15 at 19:02
  • @MikeM So you have replicated DBs that get updated and inserted into regularly at the replicated DB level, correct? Huge long-running transactions will still cause the log file to grow in any recovery mode. If backups aren't needed, just keep them set to SIMPLE and see how it goes, but I thought with replication the logs are truncated at replication regardless. What version of SQL Server you're running all this on and setup how? Generally, data redundancy isn't meant to be a replacement for data backups as far as I know--your case may be unique perhaps--I assume your prod DBs are backed up? – Pimp Juice IT Oct 30 '15 at 19:46
0

if you have a production database that is in use and has changes, in my experience, you should change the recovery model to full or bulk-logged at least, you also need transaction backups so the log file wont get large. although having replication can help you in recovering some of your data (replicated data), but you should never think of it as a backup. having full recovery model not only is important for transaction backups but it also gives you recovery options in case of a data loss that you don't have with simple recovery model. so I suggest you use full recovery model for all your databases.

this link, has a very useful information you can use.

  • No, No, No. These servers are REPLICATION SUBSCRIBERS, transactional replication, one way. In a way, they are backups of data. – Mike M Oct 30 '15 at 14:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.