Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

AG-Read only replicas Expand / Collapse
Author
Message
Posted Tuesday, July 8, 2014 9:17 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, July 15, 2014 8:13 PM
Points: 124, Visits: 750
We are planning to have read only replicas in our environment. Current setup holds one pair of synchronous nodes in same data center and other node asynchronous commit in different data center. We would like to use all three nodes as read only. Is this possible?
Post #1590586
Posted Wednesday, July 9, 2014 5:36 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 7:39 AM
Points: 1,286, Visits: 1,088
As far as I'm aware, you can have up to 4 secondary replicas in SQL 2012 and up to 8 in SQL 2014. So you should not have a problem with setting up 3 secondary read only replicas in your environment.

Overview of Always On - http://msdn.microsoft.com/en-us/library/ff877884(v=sql.110).aspx

Andrew
Post #1590681
Posted Wednesday, July 9, 2014 7:40 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, July 15, 2014 8:13 PM
Points: 124, Visits: 750
Thanks Andrew. What i am looking for is how to balnce these read only connections between one read write, two read only nodes. all the writes will be hitting the read write node. when it comes to reads how the traffic gets diverted between three nodes. also we are planning to introduce load balancer to manage the read traffic. but in Ag the listener checks for synchronous read only replicas and diverts the read only traffic. the other replica is set for asnchronous commit. how the read traffic will get forwarded to this node?
Post #1590740
Posted Thursday, July 10, 2014 5:32 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 7:39 AM
Points: 1,286, Visits: 1,088
This link should give you some information about diverting read only traffic:-

http://msdn.microsoft.com/en-us/library/hh710054.aspx#RORReplicaProperties

However if you want to split the traffic between read only replicas, I'm honestly not too sure.
Post #1591095
Posted Thursday, July 10, 2014 8:49 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, July 15, 2014 8:13 PM
Points: 124, Visits: 750
Andrew,

Is there anyway you can help me out in figuring how this read only routing is made. As far as my knowledge goes, client connections connect to listener and from there connects to primary. But if the applicationintent is equal to readonly then they will be diverted to readable secondary replicas. So the read only client connections will have to connect to primary then diverted to secondary? Am I right?
Post #1591410
Posted Friday, July 11, 2014 9:45 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, September 26, 2014 12:45 PM
Points: 317, Visits: 817
We've been using config like this for a few years. Besides the the primary we have one sync nonreadable replica for HA, one async readable replica for reporting and one more async nonreadable replica for DR.

We had some initial difficulty pushing out the connection string change for applicationintent (older clients), so we just have a DNS entry that gets users/apps to the SQL instance with the readable replica.

FWIW, we're in process of moving back to FCIs for HA--using AGs for HA has not been great experience. Might want to consider this if you're not too far down that path. We still are big fans of using AGs for the readable replica capability and DR, just not for HA.



Post #1591695
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse