October 2, 2006 at 5:25 am
We're having a discussion here at work on what's needed for a proper replication process. Among other things it is stated, that the recovery model should be set to FULL. I wonder why this is?
Mind, I do know the differences between the 3 recovery models. Many of our databases are set to simple recovery, because in the evening all the data of the current day would be overwritten with an official datastream. It's not such a big deal to change the recovery to FULL, but as I said, I wonder why that would be necesarry?
Greetz,
Hans Brouwer
October 3, 2006 at 5:05 am
What type of replication? For merge replication I could see that you might want the transaction logs backed up in case you need to restore to the point in time. If data gets corrupted on a subscriber, then it would replication to the publisher, or other subscribers. Would you then restore from the previous night?
I suppose it still relates to the same question as to how you would want to recover the data.
October 3, 2006 at 5:21 am
Tnx for responding.
I realise very well that a merge-repl needs a full recovery model. I should have said this situation is a transactional replication, realtime. The target database is read-only, other situation is described in my first posting.
In this situation I see no benefit for full recovery mode.
Greetz,
Hans Brouwer
October 3, 2006 at 11:23 am
the recovery model will only impose a restriction on your point-in-time restore. You can use *any* of the three.
When combining technologies though, Like log shipping or DB Mirroing, Log truncation is not an option and only then you are left with full or Bulk-logged.
Cheers,
* Noel
October 4, 2006 at 6:38 am
By default logs used for databases with transactional pubs are not truncated until the logreader clears the transaction. There is a switchover somewhere that overrides that behavior - but you need to be on your game if you plan to use it! So as long as the log reader is running transactions will get cleared quickly and if you're in simple mode, log size should remain reasonably stable.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply