Sybase Replication Server conflict resolution


Does Sybase Replication Server support conflict resolution automatically? If so, can anyone please explain how rep server resolves conflicts? By conflicts, i mean updates or deadlocks etc

I'm trying to compare with Oracle replication capabilities...

Who is Participating?
Joe WoodhouseConnect With a Mentor Principal ConsultantCommented:
Sybase replication uses normal Sybase ASE transaction management to deal with readers vs writers and writers vs writers. Everyone queues up behind a writer.

But I think you mean, what happens if two different sites both update a row with the same PK? There is no business-logic conflict resolution, this is treated as two sequential updates to the same row. Repserver doesn't see this as a conflict because in terms of database locking, it isn't.

If this is the sort of thing you mean, you'll need to do this yourself. A common approach is to include some kind of siteID in each PK which makes each row at each location distinct. If two sites try to write to the otherwise-identical row, you'll need to detect and manage that yourself.

Basically RepServer's job is to deliver transactions. It's up to you to make sure the transactions it delivers are the right ones.
I think you should explain it more. Oracle concepts are different than the ones in Sybase. I am not sure why Oracle needs conflict resolution in replication? It may not be relevant for Sybase replication. Maybe you can give an example.
alpmoonConnect With a Mentor Commented:
I think the concept of "conflict resolution" is relevant to snapshot replication. It is not relevant for log based asynchronous replication. As Joe explained clearly asynchronous replication requires updates to be applied in the order of transaction sequence at source.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.