You can do that with merge also. Neither one will resynchronize, but both
views on the subject. It does not represent the views of any other person
"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:uRcaDitKGHA.2012@TK2MSFTNGP14.phx.gbl...
> Not with merge. With transactional you can do a nosync, and then a
> validation to determine exactly which tables are out of sync, and manually
> fix them.
>
> --
> 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 >
> "Huy (Andrew) V Nguyen" <andrew.nv@gmail.com> wrote in message
> news:43e6cae6$1@dnews.tpgi.com.au...
>> Hello,
>>
>> I installed replication on 2 computers. Both running MS WIndows XP with
>> MSDE 2000 SP3a. My mistake was to leave the retention period to be 14
>> days. The user unfortunately leave it for more than 1 month until trying
>> to synchronize. Now since the subscription has expired and no meta data
>> left, it seems that it does not work anymore.
>>
>> My question is: Is there any way we still can synchronize without having
>> to lose data. I used redgate data compare to check and it has few
>> thousands records difference.
>>
>> Thank you very much for any help
>
>