By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,715 Members | 1,815 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,715 IT Pros & Developers. It's quick & easy.

One distributor is re-sending transactions another stops sending altogether.

P: n/a
I'm running SQL Server 2000 SP2 transactional replication.
Periodically replication fails due to primary key errors. On
investigation I find that the offending transaction is attempting to
insert a duplicate of a recently replicated row (identical data
including the rowtimestamp, which is automatically generated in the
publishing database). My conclusion is that the distributor is
sending the same transaction twice. There is usually a large block of
transactions that are duplicates. Replication has been removed and
reinstalled with no change. Any suggestions on what might be causing
this problem?

Another distributor/publisher replicating to the same subscriber is
having the opposite problem. When replication is first set up,
everything works fine. Then, a few hours or days later, I notice that
no new transactions have been replicated for some time. The
distribution agent appears to be running normally with no errors and
no transactions are queued in the distribution database. The
subscription and publication are still active but new data stored to
the published articles that should be replicated are ignored. Again
any suggestions on how to proceed would be greatly appreciated.

We have many other systems replicating with no problems, some to the
same subbscriber and built from the same image. I plan to re-install
SQL Server on both of these systems when operations allow, but I would
really like to find the root cause of this problem.


Walt Smith
Jul 20 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.