Replication conflict resolver

Hi Everyone!
Here another post on replication.

When conflict occur, I want the user to be able to select witch row to keep and witch to delete.

I've look for system stored procedure, that could help me do the resolution but I've founded nothing.

So I've thought that I could do it by hand, with UPDATE/DELETE query
Take the row in the %TABLE_NAME%_Conflict table and copy it into the real table, than delete the row.

I this the good way of doing it?

Is there any other way?

Thanks !No one, here have a custom conflict resolver ?|||

Hi Zakary,

It sounds like you are wanting to replicate - excuse the pun - the interactive conflict resolver.

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/repref9/html/56cb122d-9b1e-4f79-81de-0118023d1004.htm

and ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rpldata9/html/172c60c7-f605-4eb5-b185-54ae9e9d3c60.htm

|||

Thanks For your reply!

Those help topic, is about SQL 2005 and I’m using MSDE(SQL 2000).

I don't want to use SQL Conflict resolver, but a custom VB .NET Front-end, to resolve conflict. And I was wondering if my approach is appropriate or not.

Thanks

|||

Here is a sql 2000 link.

http://msdn2.microsoft.com/en-us/library/aa179421(SQL.80).aspx

I was thinking that although this might not give you exactly what you want you might be able to copy how it works functionally.

Cheers, James

Replication - Conflicts

Hello,
I read in articles that there can occur two kinds of conflicts during
replication and that the SQL Server Reconciler solve such conflicts:
1) If more subscriber try to modify a row on the publisher database at the
same time.
2) If a certain row is modified at the subsriber database as well as the
coresponding row at the publisher database. So any one of those two have to
win and the other win will accept the changes of the other side.
So how does it look like when the Reconciler solve these two conflicts. How
does it work?
thx
rob
Hello,
Sorry that I posted the same question twice but it was accidentally. But
unfortunately this information is very important for me. Does no one knows
how the SQL Server Reconciler solves these conflicts (propagated by Hilary
Cotter)?
1) primary key collisions, where the publisher and subscriber enter a row
with the same value for the primary key between merge agent runs
2) a row is updated on the publisher or subscriber and deleted on the
subscriber or publisher. When the merge agent runs it attempts to update a
row which no longer exists.
3) you update the same row on both sides of a replication solution and do
not have column level tracking enabled for your publication.
Thank you very much in advance.
Regards
mat

Replication - can subscriber objects be pre-existing?

My manager does not want to go through the process of moving 40 GB of data to the subscriber database over the network as would occur during the initialization phase of replication (exact method of replication has yet to be determined). The subscriber db is for Web Access and will be read-only. He wants to back up a db and use tapes to restore the db on the subscriber db server, and then activate replication. I have told him that you have to allow SQL Server to create the objects on the subscriber side and you have to allow SQL Server to control the data flow, that manually creating the objects on the subscriber side will not work. He says that I am incorrect.

Who is right? I haven't been able to find an answer from the Microsoft site and news groups.

Thanks,I hate to be the bearer of bad news for you, but your manager is correct in this instance.

Here's the link to get you started:

http://support.microsoft.com/kb/320499/en-us

It really does speed things up!

Tom