31
Mar
Off

How to handle expected replication errors

I have a central SQL Server that handles push merge replication with SQL Servers in remote branches.

These are often not available. Since the replication is executed on a high frequency the Windows Application Eventlog ist filled with Error Messages.

I found no better solution than disabling the error loging relevant message number via

sp_altermessage 14151, 'WITH_LOG', 'false';

Now the Replication Job still has a history with failed executions, the SQL Log is also correct but the Windows Application Eventlog doesn’t show the Errors nomore.