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?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.
Joe WoodhousePrincipal 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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Sybase Database

From novice to tech pro — start learning today.