RE: Transactional replication: Deadlock issue

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

If you just initialize the data betweek DB1 and DB2 without DB3 being
affected then won't there be non-convergence with DB3? If there are rows now
in DB2 and not in DB3 which the distribution agent updates, there will be an
error from the merge agent as it tries to apply the changes on the
subscriber. I'm assuming that there aren't relevant filters which will
prevent this.
I'm wondering whyt there are tables which are being republished in the merge
publication. Would it be possible to have the transactional publication
publish to DB3 and just have the merge publication apply to the remaining
tables.
We probably need to understand the topology and schemas a bit more to form a
proper set of advice.
Cheers,
Paul Ibison

.

Relevant Pages

  • A00 : Links zu externen Tabellen (BE)
    ... DB2 = von der DB1 gestartete FE DB ... Tab's in der DB3 mit dem LinkManager aktualisiert werden. ... Dim ws As DAO.Workspace ...
    (microsoft.public.de.access)
  • Re: Transactional replication: Deadlock issue
    ... subscirber, allow subscriber changes)-->DB3 ... System2 with DB3's as database). ... intermediate db server DB2 and set up merge replication between DB2 ... affected then won't there be non-convergence with DB3? ...
    (microsoft.public.sqlserver.replication)
  • Getting errors while trying to use new Mysql 50 port and pkg
    ... One (db2) is running FreeBSD ... The other, (db3) on a new ... Db2 is running mysql 5.0.24a and has been working ...
    (freebsd-questions)
  • How to know if a database is not available
    ... Insert into DB3 ... Select field1, field2 from DB1 ... Select field1, field2 from DB2 ... Select 'One of databases is not available','0' ...
    (microsoft.public.windows.server.general)