Hi all,

I use merge replication with windows CE clients and SQL Server 2005.

I have an issue which I didn't get solved yet:

1. If someone collects data in an existing table on the client
(subscription exists) and the publication on the server is changed in
the meantime. After replication all new data is lost.

2. If someone collects data in an existing table on the client (the
table and schema is made on the client). After new subscription and
replication all new data is lost.

Do I have to handle this manually or is there a configuration to
preserve collected data on the client side?

Thanks a lot
Roman

I am not totally clear on what you are describing. Let me try to explain how
it works which may or may not be what you are seeing.

1) If you change the data on either side the merge replication process will
merge the data. There may be conflicts updating the same row on both sides
between syncs, update a deleted row, or a row was entered on both the
publisher and subscriber with the same pk value which will cause data to be
lost. You can control this behavior by partitioning to eliminate chances of
this occurring or to use a custom or one of the default resolvers.

If you change the publication in some way, there is an option to upload
subscriber changes before the new snapshot comes down. This option is the
upload subscriber changes before the reinitialization by setting
SqlCeReplication.ReinitializeSubscription.uploadBeforeReinitialize to true.

2) If you send a new snapshot down it does whack all data, unless you
specify the uploadBeforeReinitialize to true.

HTH
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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]