I'm confused about the expected functionality and interoperability of availability groups and transactional replication. We would like our published DB to be part of an availability group. We have that up, but when we fail over to the secondary, replication doesn't not function as new DML occurs in the secondary (now primary). It does pick back up after we fail back to the original primary. Is there a way to configure it such that replication continues seamlessly after a failover?
Thank you!
-Peter
PS Here is what replication monitor has to say when the original primary is down:
"replicated transactions are waiting for the next log backup or for the mirroring partner to catch up"