4

I have two SQL Server DB instances on the same machine with one hosting a replica of the other.

In addition, I have transaction replication setup for all tables on the main instance to the replica.

I have verified that the log reader and associated agents are all running. However, one of the log reader agents says, "Replicated transactions are waiting for the next Log back up or for mirroring partner to catch up".

I have done a transactional log backup to trigger it but to no avail; tried deleting the subscriber and publisher and recreating it again…but still end up with this message.

Paul White
  • 94,921
  • 30
  • 437
  • 687
Andrew B.
  • 41
  • 1
  • 2

1 Answers1

1

on this answer the trace flag 1448 is advised:

Also, since you are using always-ON with T-Rep, I would suggest you to enable TF 1448.

Trace flag 1448 enables the replication log reader to move forward even if the asynchronous secondary replicas have not acknowledged the reception of a change. Even with this trace flag enabled,, the log reader always waits for the synchronous secondary replicas. The log reader will not go beyond the min ack of the synchronous secondary replicas. This trace flag applies to the instance of SQL Server, not just to an availability group, an availability database, or a log reader instance. This trace flag takes effect immediately without a restart. It can be activated ahead of time or when an asynchronous secondary replica fails.

Reference : Configure Replication for AlwaysOn Availability Groups

However, on this other answer here, it is not:

I would absolutely not enable this if you care about your replication setup and data integrity. It allows for uncommitted transactions to be sent to subscribers which can lead to data incorrectness in the event of a failure. You'll have to go manually fix your data in the distributor/subscriber at that point.

Marcello Miorelli
  • 17,274
  • 53
  • 180
  • 320