I think that it happens because if a subscriber stay more that 7 days without sincronizing, then the data is considereted unvalid

Do you think that the problem is this:

"The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Publisher for changes not yet sent to the...

Some log information from SQL Server log:

2015-11-13 16:38:02.51 spid97 Replication-Replication Merge Subsystem: agent 0043007B-0045-0045-4500-320036003800 failed. The reconciler process was stopped because the Subscriber that initiated...

I also run the sp_who2 and I see same lines with

56 SUSPENDED ...

Also, In the waiting category logging is above all others with this values:

wait time 13000

average waiter count 14.7

Recent wait time = wait time

It sounds like a log issue or a...

I want to test merge replication. I would like to create one. I only have one computer so can I create the merge replicaton (configure the distribuition and subscribers) all...

I mean using having the publisher database and the subscriver database on the same instance?

How can I add figures like you just did?

thanks

no, from 5 to 5 seconds

thank you

When a user transaction is committed (either explicitly via a COMMIT statement, or implicitly), SQL Server writes all changes from the Log Cache out to the log files on disk....

If I add an additional transaction log (on other disk) to the database that would devide the i/0 between logs . which would help, correct?

I belive that 77% is a...

I am trying to see why some data is taking more time to be distributed.

For instance, this result:

WaitTypeWait_SResource_SSignal_SWaitCountPercentageAvgWait_SAvgRes_SAvgSig_S

WRITELOG1428099.931381452.4146647.5233103900276.980.00430.00420.0001

The log write percentage is almost on 77% ? is this normal ?