July 30, 2012 at 8:45 am
What does this exactly mean? Is it almost the same as restoring the subscriber to match with the snapshot data? If that's the case what is the meaning of 'sync unsynchronized data before snapshot' option.
I noticed that when I check that option, any data changes made after snapshot is created, still show up in the db after snapshot is applied. So what is the use of applying the snapshot then? Can anyone please point me to some articles on this. Thanks for your time.
July 31, 2012 at 7:53 am
Start with Books Online. Every question you asked is answered in there.
A snapshot is a starting point for replication. Replication can't keep track of every transaction forever, so it needs to have a starting point. If you are initializing from a snapshot, it is your starting point. It applies the snapshot to the subscriber when you initialize it and then starts synchronizing transactionally from that point forward (from the point that the snapshot was created, not when it is appleid).
There are other ways to initialize a snapshot such as from a backup file or manually (nosync). How you initialize it originally affects how it is reinitialized. For example, if you initialize from a backup, you have to reinitialize from a backup.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply