Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ruchirj07
Starting Member
37 Posts |
 Posted - 2007-10-03 : 02:46:01
|
| Hi,I have 2-3 tables which contains are getting conflict error "Primary Key Violation" because the Same Primary Key is getting updated both at Publishing end and Subscribing end.Can this be resolved any how without any manual intervention?Regards,Ruchir |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2007-10-03 : 02:48:39
|
| the primary key should never be updated. Are you saying that the value used for the primary key is being changed or that that particular row of data (excluding primary key values) is being changed at both the publisher and subscriber.I should think that if both rows were being updated simultaneously that you would just have to using the conflict handler.-ec |
 |
|
|
ruchirj07
Starting Member
37 Posts |
Posted - 2007-10-10 : 09:28:06
|
| Thanks. But conflict handler does not overwrite the data of Distributer on Subscriber, it rather just logs the conflict in the logs which one has to view everyday manually, if the scenario is happening every day.Is there any setting for the conflict handler which is to be made while setting up the distributor or replication for matter. |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2007-10-10 : 15:59:15
|
| You can control the merge conflicts with the default resolver or with custom resolvers. It is actually quite easy. You can also roll your own if the built in stuff doesn't work for you. Here is the best article i have found on how this all works. It should be similar in SQL2K5, although I don't have any merge rep running on our 2K5 boxes so i can't say for sure.http://www.sqlservercentral.com/articles/Replication/handlingconflictsinmergereplication/2258/-ec-ec |
|
|
|
ruchirj07
Starting Member
37 Posts |
Posted - 2007-10-19 : 05:18:59
|
| This is what, do not have option of custom resolver in sql2k5 :( |
|
|
|
|
|
|
Conflict in merge prelication