I've been using replication for a while so I'm after some clarification really..I think we have a process issue but I just wanted to eliminate replication.
We are using SQL2008 Ent
I have a database A which is located in India and is merge replicated every minute to another database B in London. Database B is then transactionally replicated to a database C on a different server in London. This is run every hour from say
midday to 6pm. That works fine.
The Logreader on the server with database B is running continuously.
My question(s) concerns transactions:
1.The logreader will only capture commited transactions. The merge procedures apply each table changes as a single transaction so while the merge agent is running there will be committed and non committed transactions is this correct or is each cycle of
the merge agent considered as a single transaction?
2.If the distribution agent runs (on database B to push to database C) to capture the changes and the merge agent is also running and applying updates to database B, is it possible that only part of the merged data is captured and distributed to
database C or will the distribution agent continue to run until the merge cycle has completed ?
View Complete Post