You have the option to upload the changes as the subscriber if you do a
reinitialization. When you right click on your publication and select
reinitialize you will get this option.

Signature
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
> When a subscriber has exceeded the retention period since the last sync,
> I've heard that it can upload it's changes to the publishser then
[quoted text clipped - 4 lines]
> Thanks,
> Troy
Troy Wolbrink - 30 Nov 2005 03:04 GMT
Thanks for that information. I'll definitely have to look into this a bit
more. I want to determine if those "changes" include deletes as well. Also
I want to determine if conflict detection is possible. I'm assuming that
it's probably not always possible since the publisher is past the retention
period (and thus might not have all the change information necessary to
determine this).
Also, I'd like to find out if this "upload the changes" process can be used
to combine all the records from a new databases to the publisher? (ie. a
new client wants to include all their existing data and then start (init) a
new subscription. Perhaps it might be better to write custom code for this?
--Troy
> You have the option to upload the changes as the subscriber if you do a
> reinitialization. When you right click on your publication and select
> reinitialize you will get this option.
>> When a subscriber has exceeded the retention period since the last sync,
>> I've heard that it can upload it's changes to the publishser then
>> reinitialize the subscription. How is this upload handled? Is this a
>> manual process? Or is this case specifically handled by merge
>> replication?