I have one table in Merge Replication with dynamic filtering and
exchangetype=2 (from publisher to subscriber only), with Merge Agent
scheduled daily (night)
In this table I insert tipically some rows between two agent's run and I
would like to replicate each row as single transaction (i.e. what's happen if
I must to replicate three rows to a subscriber in single agent run but after
replication of first row network link between publisher and subscriber goes
down?).
Can I obtain this with three insert with three transactions on publisher
table (one insert, one transaction)?
Thanks in advance
Alexago,
unlike transactional, merge replication doesn't really have a concept of
transactions. Generation numbers are used as a logical clock, but this is a
different mechanish (see BOL). If the network link goes down, you can just
restart the merge agent and it will continue where it left off. If you are
concerned about the article processing order, have a look at this article:
http://support.microsoft.com/default.aspx?scid=kb;[LN];307356
HTH,
Paul Ibison
Saturday, February 25, 2012
Merge Replication and transactions
Labels:
agentscheduled,
andexchangetype2,
database,
dynamic,
filtering,
merge,
microsoft,
mysql,
oracle,
publisher,
replication,
server,
sql,
subscriber,
table,
transactions
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment