Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Transaction Integrity during replication

2 posts in General Discussion Last posting was on 2012-07-09 17:34:12.0Z
Rex Jones Posted on 2012-07-06 18:47:41.0Z
Sender: 10ae.4ff73095.1804289383@sybase.com
From: Rex Jones
Newsgroups: sybase.public.rep-server
Subject: Transaction Integrity during replication
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4ff732cd.10f7.1681692777@sybase.com>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 6 Jul 2012 11:47:41 -0700
X-Trace: forums-1-dub 1341600461 172.20.134.41 (6 Jul 2012 11:47:41 -0700)
X-Original-Trace: 6 Jul 2012 11:47:41 -0700, 172.20.134.41
Lines: 14
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9213
Article PK: 870371

I wanted to see what folks thought about transaction
integrity during replication. It is understood that the
integrity is provided at a transaction level. But a logical
transaction can contain write to one or more tables. If its
more than one table, does the order in which the statements
are picked up and applied still syncrhonous or asyncrhonous?
Is there any chance of orphans (in a parent-child type of
scenario where constraints are not enforced at both primary
and replicated sites but enforced at the application level)
being introduced?

Any pointers in this regard would be nice.

_Rex


Manish Negandhi [TeamSybase] Posted on 2012-07-09 17:34:12.0Z
From: "Manish Negandhi [TeamSybase]" <negandhi.manish_nosmap@gmail.com>
Newsgroups: sybase.public.rep-server
References: <4ff732cd.10f7.1681692777@sybase.com>
Subject: Re: Transaction Integrity during replication
Lines: 42
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4ffb1614@forums-1-dub>
Date: 9 Jul 2012 10:34:12 -0700
X-Trace: forums-1-dub 1341855252 172.20.134.152 (9 Jul 2012 10:34:12 -0700)
X-Original-Trace: 9 Jul 2012 10:34:12 -0700, vip152.sybase.com
X-Authenticated-User: teamsybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9214
Article PK: 870374


<Rex Jones> wrote in message news:4ff732cd.10f7.1681692777@sybase.com...
>I wanted to see what folks thought about transaction
> integrity during replication. It is understood that the
> integrity is provided at a transaction level. But a logical
> transaction can contain write to one or more tables. If its
> more than one table, does the order in which the statements
> are picked up and applied still syncrhonous or asyncrhonous?
> Is there any chance of orphans (in a parent-child type of
> scenario where constraints are not enforced at both primary
> and replicated sites but enforced at the application level)
> being introduced?
>
> Any pointers in this regard would be nice.
>
> _Rex

Sybase replication server uses asynchronous mechanism to apply transactions
at replicate. In other words, it does not use tight-consistency or so
called two phase commit. Transaction at primary can commit without knowing
status of replicate side. Having said that replication server ensures commit
order as well as "state consistency" of primary side while applying
transactions at replicate side. Multi table transactions are very common in
replication environment.. Replication server ensures that commit order of
the transaction is always maintained. If transaction contains more than one
table , it is applied exactly in order it was applied in primary and
therefore there is no chance of orphans





-HTH

Manish Negandhi

[TeamSybase]