Skip to main content

Timeline for Transaction Replication on AlwaysOn

Current License: CC BY-SA 3.0

8 events
when toggle format what by license comment
Apr 18, 2017 at 15:40 vote accept reshad
Apr 18, 2017 at 15:35 comment added reshad I'm going to vote your comment for the best answer. The flag worked for me without changing my commit statues from SYNC to ASYNC. However, I'm going to a add a piece in here to run EXEC sp_replicationdboption 'YOURDATABASE/DISTRIBUTION','sync with backup',false which provokes that the transaction shouldn't be backed up, and can be replicated. Thanks again for the good comment.
Apr 18, 2017 at 14:37 comment added reshad I think to solve this issue, based on your suggestion, I have to apply a sync primary, Asyn secondary, and turn on the flag?
Apr 18, 2017 at 13:14 comment added AMtwo There is no way to make the log reader read past transactions that are uncommitted at the synchronous secondary. I've updated my answer with a little bit more detail on that aspect. Essentially, if you lose a synchronous replica, Replication won't consider the transaction fully committed, and won't replicate that transaction.
Apr 18, 2017 at 13:13 history edited AMtwo CC BY-SA 3.0
Add explanation on why the TF won't affect synchronous replicas
Apr 18, 2017 at 13:05 comment added AMtwo I copy/pasted that link from MSFT documentation. Looks like the link is bad in their documentation, and I just copied the bad link. I've removed the link from my answer--if I can find an updated link, I'll add it back in.
Apr 18, 2017 at 12:49 comment added reshad thanks for the great comment, I think this is a fix where Asyn commit is applied, but I have AG in Symc commit, and want to keep it that way due to the flavor of automatic failover. Any workaround for this? can you repost the link, it didn't work for me?
Apr 18, 2017 at 0:51 history answered AMtwo CC BY-SA 3.0