After you create one listener through SQL Server, you can add an additional listener, as follows: 1. Create the listener using either of the following tools:
• Using WSFC Failover Cluster Manager:
i. Add a client access point and configure the IP address. ii. Bring the listener online.
iii. Add a dependency to the WSFC availability group resource.
For information about the dialog boxes and tabs of the Failover Cluster Manager, see User Interface: The Failover Cluster Manager Snap-In.
• Using Windows PowerShell for failover clusters:
i. Use Add-ClusterResource to create a network name and the IP address resources. ii. Use Start-ClusterResource to start the network name resource.
iii. Use Add-ClusterResourceDependency to set the dependency between the network name and the existing SQL Server Availability Group resource.
For information about using Windows PowerShell for failover clusters, see Overview of Server Manager Commands.
2. Start SQL Server listening on the new listener. After creating the additional listener, connect to the instance of SQL Server that hosts the primary replica of the availability group and use SQL Server Management Studio, Transact-SQL, or PowerShell to modify the listener port. For more information, see How to create multiple listeners for same availability group (a SQL Server AlwaysOn team blog).
Related Tasks
• View Availability Group Listener Properties (SQL Server) • Remove an Availability Group Listener (SQL Server)
Related Content
• Microsoft SQL Server AlwaysOn Solutions Guide for High Availability and Disaster Recovery • SQL Server AlwaysOn Team Blog: The official SQL Server AlwaysOn team blog
See Also
AlwaysOn Availability Groups
Client Connectivity and Application Failover (AlwaysOn Availability Groups)
Add IP Address Dialog Box (SQL Server Management Studio)
This F1 help topic describes the options of the Add IP Address dialog box. This dialog box accessed from the New Availability Group Listener dialog box and the Listener tab of the
Specify Replicas page of the New Availability Group Wizard or the Add Replica to Availability
Group Wizard of SQL Server 2012.
Prerequisites
Before you begin to add subnets to an availability group listener, ensure that know the IP address for each subnet and, for an IPv4 address, the subnet mask.
Add IP Address Options
Subnet
Use the drop list to select an address for the subnet that you are adding to the availability group listener. By default a subnet possesses both an IPv4 address and an IPv6 address. The
first time you use the Add IP Address dialog, the Subnet drop list displays both subnet addresses for each subnet that hosts a replica for the availability group. To add a given subnet to the listener, select one of its subnet addresses.
After you complete the Add IP Address dialog box and click OK to add a selected subnet address to the listener, the Subnet drop list filters out that subnet address. All unselected subnet addresses remain on the drop list. Be sure that you add one and only one subnet address per subnet to the listener, or listener creation will fail.
Addresses
Use this field to enter a static IP address for the selected subnet address. Contact your network administrator for this IP address. Ensure that you enter a valid address for the selected subnet address, or listener creation will fail.
IPv4 Address
If you selected the IPv4 subnet address of a subnet, enter a valid IPv4 static address here.
Subnet Mask
For an IPv4 address, this read-only field displays the subnet mask of the selected subnet.
IPv6 Address
If you selected the IPv6 subnet address of a subnet, enter a valid IPv6 static address here.
OK
Click to create add the subnet whose address you selected, along with the static IP address that you specified. A row containing these values will be added to the subnet grid of the New
Availability Group Listener or Specify Replicas dialog box. Important
The Add IP Address dialog does not verify the IP address. Also the dialog does not prevent you from adding the second subnet address for a subnet that you have already added to the availability group listener.
Cancel
Click to cancel your selections, and return to the New Availability Group Listener dialog box or Listener tab without adding a static IP address for any subnet.
Related Tasks
• Create or Configure an Availability Group Listener (SQL Server) • Use the New Availability Group Wizard
• Use the Add Replica to Availability Group Wizard
See Also
Client Connectivity and Application Failover (AlwaysOn Availability Groups)
Prerequisites, Restrictions, and Recommendations for AlwaysOn Client Connectivity (SQL Server)
Configure Read-Only Routing for an Availability Group
To configure an AlwaysOn availability group to support read-only routing in SQL Server 2012, you can use either Transact-SQL or PowerShell. Read-only routing refers to the ability of SQL Server to route qualifying read-only connection requests to an available AlwaysOn readable secondary replica (that is, a replica that is configured to allow read-only workloads when running under the secondary role). To support read-only routing, the availability group must possess an availability group listener. Read-only clients must direct their connection requests to this listener, and the client's connection strings must specify the application intent as "read- only." That is, they must be read-intent connection requests.
For information about how to configure a readable secondary replica, see Configure Read-Only Access on an Availability Replica (SQL Server).
• Before you begin:
Prerequisites
What Replica Properties Do you Need to Configure to Support Read-Only Routing? Security
• To Configure read-only routing, using:
Transact-SQL PowerShell
Configuring read-only routing is not supported by SQL Server Management Studio. • Follow Up: After Configuring Read-Only Routing
• Related Tasks • Related Content
Before You Begin
Prerequisites
• The availability group must possess an availability group listener. For more information, see Create or Configure an Availability Group Listener.
• One or more availability replicas must be configured to accept read-only in the secondary role (that is, to be readable secondary replicas). For more information, see Configure Connection Access on an Availability Replica (SQL Server).
• You must be connected to the server instance that hosts the current primary replica.