Azure-docs: Number of load balancer

[danvalero]

It is not clear for me in the document if I need a load balancer for the listener and another for the WSFC CAP or if I can have one single Load Balancer with multiple frontend.

Can you provide guidance about it?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 09504e18-c72f-07ee-3ef8-dc9ed44562ca
• Version Independent ID: 8058bb4f-2321-ddf2-9930-0cc767b68a62
• Content: Configure availability group listeners & load balancer (Azure portal) - SQL Server on Azure VM
• Content Source: articles/azure-sql/virtual-machines/windows/availability-group-load-balancer-portal-configure.md
• Service: virtual-machines-sql
• GitHub Login: @MikeRayMSFT
• Microsoft Alias: mikeray

[VikasPullagura-MSFT]

@@danvalero
Thanks for your Question! We are checking on this and will get back on this.

[danvalero]

Doing some research I found that the same Load Balancer can be used at https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-manually-configure-tutorial

I think updating the document related to this issue would allow other people save time when working with this kind of scenarios

[psmanhas]

@danvalero Thank you for the feedback.We will work on it and will keep you updated on the thread.

[psmanhas]

@danvalero Same Load Balancer can be used for both purposes with different Front ends. Also, note that if using WS 2019 then you won’t need any ILB setting for WSFC CAP as the CAP would be accessible by default.Do let me know in case of any further concerns.

Thanks

[danvalero]

Thanks for the note on WS 2019. Is it documented somewhere? I could not find anything about it

[kfarlee]

There is a WSFC feature in Windows Server 2019 called Distributed Network Names (DNN) Using this feature enables you to have the same functionality without needing to configure a load balancer at all.
While it is possible to share the same ILB between the CAP and SQL Serve, in general we'd like to not constrain the Cluster Access Point to being hosted on the same node as the SQL Server FCI or Always on Availability Group. So for that reason we generally see separate access points. Again, if you have the option of running on Windows 2019/SQL 2019, do look into DNN technology which eliminates the need for the ILB.

[rothja]

assign:kfarlee

[psmanhas]

@danvalero Hope the provided information is helpful.

We will now close this issue. If there are further questions regarding this, please tag me in a comment. I will reopen it and we will continue the discussion.