Can you setup Replication with AlwaysOn?
Configure the Always On Availability Group If using the Availability Group Wizard, you can either allow the wizard to initially synchronize the secondary replica databases or you can perform the initialization manually by using backup and restore.
How do AlwaysON availability groups work?
The Always On availability groups feature is a high-availability and disaster-recovery solution that provides an enterprise-level alternative to database mirroring. An availability group supports a failover environment for a discrete set of user databases, known as availability databases, that fail over together.
How to configure a subscriber availability group for replication?
For transactional replication, use the following steps to configure and failover a subscriber availability group: Before creating the subscription, add the subscriber database to the appropriate Always On availability group. Add the subscriber’s availability group Listener as a linked server to all nodes of the availability group.
What happens when an always on availability group fails?
When an Always On availability group containing a database that is a replication subscriber fails over, the replication subscription might fail. For transactional subscribers, the distribution agent will continue to replicate automatically if the subscription is using the name of the availability group listener of the subscriber.
Can a distribution database be placed in an availability group?
Placing the distribution database into an availability group is supported with SQL 2016 and greater, except for distribution databases used in merge, bidirectional, or peer-to-peer replication topologies. For more information, see Configure distribution database in an availability group.
What happens when there are only two availability replicas?
When the publisher has only two availability replicas (one primary and one secondary) and a failover happens, the original primary replica remains down because the log reader does not move forward until all secondary databases are brought back online or until the failing secondary replicas are removed from the availability group.