We are planning for a migration from SQL 2008 one to many transactional replication model to SQL 2014 AlwaysON in a multi datacenter environment.We have Four datacenters and planning for six SQL Server Instances. First datacenter has three servers – One primary, one synchronous secondary and one asynchronous secondary. Remaining three datacenters will have one asynchronous secondary.
Our requirement is to sync all the changes in primary replica to the remaining five secondary replicas, Connect SQL Client to the local SQL Server(No cross datacenter calls unless there is a failure) and efficient failover management.
I have these questions. Appreciate your help and any pointers for designing AlwaysON in a multi datacenter environment.
- Is it a good idea to replace one to many transactional replication with AlwaysON for a high traffic multi datacenter application? Can I get same or better performance compared to Replication?
- In our current model, Index maintenance jobs are running at publisher as well as subscribers. We have to run these on primary because AlwaysON secondary’s are read only copies. Our total indexes size is 33 MB. Do you see any concerns if it is applied to live secondary replica?
- I assume one Windows Failover Cluster, one Availability Group and one AG Listener should be good enough for all 6 instances across four datacenters. Correct me if this is wrong.
- I would like to use AG Listener. At the same time how do I guaranty that SQL Client always connect with local SQL Server Instance(No cross datacenter calls unless there is a failure)? I don’t want to use direct SQL connection because roles are going change after the automatic failover.
Please let me know your comments even you came across these in SQL 2012.
Thanks,
SudhakarSudhakar