all groups > sql server replication > february 2006 >
You're in the

sql server replication

group:

Subscription expired


Re: Subscription expired Hilary Cotter
2/5/2006 11:47:58 PM
sql server replication:
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

[quoted text, click to view]

Subscription expired Huy (Andrew) V Nguyen
2/6/2006 12:00:00 AM
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.

Re: Subscription expired Huy (Andrew) V Nguyen
2/7/2006 12:00:00 AM
Thank you very much for your prompt reply. I use merge replication so
guess I have to get them to re-key in the data.

Andrew

[quoted text, click to view]
Re: Subscription expired Michael Hotek
2/7/2006 9:14:21 AM
You can do that with merge also. Neither one will resynchronize, but both
will tell you which tables are out of synch.

--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.


[quoted text, click to view]

AddThis Social Bookmark Button