Re: Transactional Replication 2005
- From: "Paul Ibison" <Paul.Ibison@xxxxxxxxxxxxx>
- Date: Tue, 4 Jul 2006 17:59:39 +0100
Hmmm. This PK error shouldn't be possible, assuming the data on A, B and C
is synchronized at startup. Any idea how it has occurred? This is worrying
as it implies that B is being edited, which is disallowed - only the final
server to be set up (A) can be edited and B and C must be teated as RO. If
the editing of B is temporary, you'll have to wait till you have complete
control of the system then prevent access, backup the database and restore
on A then set up the nosync initialization. Remember that after that B and C
must be RO to the users.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
.
- References:
- Re: Transactional Replication 2005
- From: Paul Ibison
- Re: Transactional Replication 2005
- From: Paul Ibison
- Re: Transactional Replication 2005
- Prev by Date: Re: Adding a distributor for merge replication
- Next by Date: Re: Snapshot agent doesn't pick new articles
- Previous by thread: Re: Transactional Replication 2005
- Next by thread: Re: Transactional Replication 2005
- Index(es):
Relevant Pages
|
