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 agent 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.
Asked
Active
Viewed 638 times
1
-
off topic but I have to ask why have the two instances on the same machine? I'd assume they are at least not using local or the same storage, but there will still be memory and cpu contention and hardware failure liabilities (making this not a DR). Just curious is all. – S3S Aug 09 '18 at 20:08
-
I hear you. I inherited this legacy system and am not a fan of the implementation. Just trying to get the subscribers established and the replication working again. – ReLeaf Aug 09 '18 at 20:37
-
no sweat. I'd post on dba.stackexchange.com -- the DBA gurus play over there – S3S Aug 09 '18 at 20:38