Listener for ReadOnlyRouting by PrinceLucifer

Active

Type:	Suggestion
ID:	772204
Opened:	11/26/2012 3:07:00 AM
Access Restriction:	Public

Workaround(s)

view

Consider this scenario:
You have an AG with two replicas, one primary, one for ReadOnly access.
Your clients are bound to only have access to specific IP ranges.
e.g. Server A has IP 10.1.1.1 Server B has 10.1.1.2, the VNN for the AG is set to 10.1.2.1, all in the same /23 subnet. The clients by firewall rules only allowed to access 10.1.2.x IP addresses.
Now that scenario works perfect for standard access via the VNN, as you can specify any IP there that the cluster can bring online. Unfortunately you can't do the same for the ROR partner.

The workaround currently is to assign each server a static 10.1.2.x IP address, which could pose several problems along the way.

Details (expand)

English

SQL Engine

Add an option to have a "ReadOnly-Listener" that will, according to the ROR-List be brought online on the node that is supposed to be the RO-Node.

Improved Administration

0 attachments

Posted by PrinceLucifer on 11/29/2012 at 10:10 PM

Right now ROR only supports one secondary anyway. (All apps that connect with ApplicationIntent=ReadOnly will end up on the same node...) That one should hold the listener

Posted by Microsoft on 11/29/2012 at 9:55 PM

Thanks for the suggestion.

Notice that there can be multiple readable secondaries, should the ReadOnly Listener bind to any of them (e.g. randomly)?

Is the problem with using ReadOnly Intent and the AG Listener that read-only connections are routed to the first available secondary (not load balanced) or something else?

Microsoft