Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


AG-Read only replicas


AG-Read only replicas

Author
Message
deep_kkumar
deep_kkumar
SSC-Enthusiastic
SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)

Group: General Forum Members
Points: 133 Visits: 756
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?
DBA From The Cold
DBA From The Cold
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

Group: General Forum Members
Points: 1788 Visits: 1728
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
deep_kkumar
deep_kkumar
SSC-Enthusiastic
SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)

Group: General Forum Members
Points: 133 Visits: 756
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?
DBA From The Cold
DBA From The Cold
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

Group: General Forum Members
Points: 1788 Visits: 1728
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.
deep_kkumar
deep_kkumar
SSC-Enthusiastic
SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)SSC-Enthusiastic (133 reputation)

Group: General Forum Members
Points: 133 Visits: 756
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?
Mike Good
Mike Good
SSC-Addicted
SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)

Group: General Forum Members
Points: 405 Visits: 1020
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.



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search