Prev: Transactional Replication from Replicated Database
Next: subscription is searching for an old snapshot
From: isbrandon on 9 Jun 2010 14:38
Hi Jeff,

This is completely unrelated to this post but I found a post of yours from a
few years back on SQLMonster that I was hoping to discuss with you.

Here is the post:
http://www.sqlmonster.com/Uwe/Forum.aspx/sql-server-replication/8310/Subscriber-Identity-Range-Mgmt-Problem-Merge-Repl

I can be reached at brandonw(a)paladinpos.com if you're able to discuss this
post. Thanks.

-Brandon

"jjones64" wrote:

> Paul,
> Thanks for the link. It doesn't appear that I have any of those types of
> scenarios going on, though. The problems are occurring more frequently as of
> yesterday and today, but there are just no indicators (job failures,
> conflicts, etc.) to indicate why this would all of a sudden occur - this
> process has worked remarkably well for 2.5 years. FYI: While I'm using merge
> replication for this process, the subscriber does not change any data, so
> it's really a 1-way sync.
>
> --
> Jeff Jones
> SQL Professional
> Atlanta, GA
>
>
> "Paul Ibison" wrote:
>
> > Jeff - did you take a look here to see if any applied:
> > http://www.replicationanswers.com/MergeNonConvergence.asp
> > Thanks,
> > Paul
> >
 | 
Pages: 1
Prev: Transactional Replication from Replicated Database
Next: subscription is searching for an old snapshot