In that case you need to look into stopping conflicts from occurring, or
find a way to handle conflicts. For instance, MS have a large article for
SQL Server 2000 here: http://support.microsoft.com/kb/315514
Rather than pick one thing that you can't change, why not include details of
your system (SQL Server versions for instance) and what you can change? That
would make it easier for someone to suggest possible ideas.
Can you change the application? For instance, have the publisher use only
odd numbers, and the subscriber only use even numbers? Or use different
seeds for your id numbers, say starting at 1 for the publisher and 10000 for
the subscriber (which of course breaks when you hit 10000 ids inserted by
the publisher, but you haven't provided any information about the expected
numbers of rows inserted so I've just picked that arbitrarily, you would
need to select a value that would allow your system to scale as required).
If you search Google for articles about SQL Server merge replication
conflicts you'll find lots of information on what you could do.
Post by saandii777
One of the solution I saw on internet is to add a column to table customer
having name of subscriber/publisher.
Thus defining cid and this column as primary key.
I know it will solve the purpose but I guess I am not in this position to
have table structure changed like this.
Someone plz help
Post by saandii777
We are facing a issue with merge replication.
Suppose I have a table customer (cid,cname) which we have published.
Note cid is primary key and it is not identity.
Initially there is one row in customer table (1,'Mohan')
After replication process
At publisher: one row is inserted with cid=2
At subscriber: one row is inserted with cid=2(allowed as working on its own
When we syncronize it throws an error as there are 2 rows with cid=2.
Note : we cannot set cid as identity.
Can anyone tell me how this issue is to be resolved.