Merge Replication - data not replicating

[jjones64]

I have a single merge publication with a single subscription that has been
working fine for the past 2.5 years but has recently had 2 instances where
edited data on the publisher has not been replicated to the subscriber.
There are no replication conflicts, errors, failed replication jobs, SQL Log
entries, or App Event Log entries that point to any 'blip' on the server.
The publisher and subscriber are on the same server, where the subscriber is
used for reporting purposes only.

Can someone possibly point me toward some additional queries or data tables
that I can look at to determine what may have happened on the merge job?

[jjones64]

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

http://www.replicationanswers.com/MergeNonConvergence.asp
Thanks,
Paul

[isbrandon]

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 ***@paladinpos.com if you're able to discuss this
post. Thanks.

-Brandon

Post by jjones64
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

http://www.replicationanswers.com/MergeNonConvergence.asp
Thanks,
Paul