Configure transactional replication for a group of Always on SQL Server 2016

Navigation
2

I have the following environment:

A server (A) that has a transactional publication, this server is not in the group of Always on

Two servers (RT1 and RT2) that are in a group of Always on

Listener (RT)

  • RT1 is the primary

  • RT2 is the secondary (Read Only)

  • RT1 and RT2 are synchronized

The RT(Listener) has two subscriptions, one for RT1 and one for RT2 . For the server that is primary ( RT1 ) it works very well since it is not Read Only , but for the secondary ( RT2 ) not causing the replicaciones are put on hold until the server ceases to be read only which happens with a failover , at that moment the replications begin to appear in the RT2 , but the RT1 as now is secondary becomes read only and starts having replications on hold.

Is there any other way to set up so that RT1 and RT2 are subscribers of the server (A) and that the replications are on both servers?

    
asked by Salo B 24.07.2017 в 19:50
source

1 answer

0

I came out following this article They are executed in the database that is being published and can only be done by code

link

    
answered by 25.07.2017 в 00:41
Use different strings.xml files regardless of Locale Increase the memory of Apache Tomcat 7