schleep (2/18/2014)
The users want some time between modifying data on the source and the mods being applied at the destination. Some changes (a typo, for example) don't need much in the way of QA. Large updates require a couple of hours to QA. And on their wildest-dreams wishlist, they could schedule changes going to the destination days in advance.
This will require some logic on your part. Replication ALWAYS delivers data transactionally. You will need to sort of authorisation process (maybe a job or application) in the form of a flag and filter to deliver data. Something like in my original suggestions would work (PUBLISH = 1).