Re: Problem with merge replication

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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



"Roman" <roman.mellenberger@xxxxxxxxxxxxxxxx> wrote in message
news:1155310746.961585.279560@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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



.

Relevant Pages

  • Re: merge Replication with a Notebook not in domain
    ... not associated with a trusted SQL Server connection. ... I have set up all SQL Server login in both publisher and subscriber.Also ... Looking for a SQL Server replication book? ... subscriber ...
    (microsoft.public.sqlserver.replication)
  • Re: Server to server Replication
    ... Replicated data is mostly read-only at the Subscriber. ... You need updates to be propagated on a transaction basis, ... Use snapshot replication or transactional replication with immediate ... Paul Ibison SQL Server MVP, ...
    (microsoft.public.sqlserver.replication)
  • NOT FOR REPLICATION clause in triggers that are replicated to subscribers are fired twice in both pu
    ... transactional replication trought VPN with updatable subscriptions to SQL ... of then marked as NOT FOR REPLICATION and copied along to the subscriber) so ... This is true for SQL Server 2000 either the insertion/update/deletion ... happens on the publisher or the subscriber: Ie, if the user is connected to ...
    (microsoft.public.sqlserver.replication)
  • Re: merge Replication with a Notebook not in domain
    ... subscriber ... Looking for a SQL Server replication book? ... The Notebook is non link to the Domain but it use a Workgroup Access to ...
    (microsoft.public.sqlserver.replication)
  • Re: SQL Mobile - cant replicate anymore?
    ... >> replicating data between SQL Mobile on my pda and SQL Server 2000. ... the replication process fails on the client. ...
    (microsoft.public.sqlserver.ce)