My name is John Marlin and I am with the High Availability and Storage Team. With newer versions of Windows Server and Azure Stack HCI on the horizon, it’s time to head to the archives and dust off ...
Updated Sep 24, 2020
Version 2.0
Blog Post
@mgraps97 Yes, this "VCO_Listener" is an example I've used. And do note the resource name of the Listener differs depending upon whether it's created via SQL Server or from PSH/CluAdmin.
Run a get-clusterresource to get the exact name & then under a planned downtime window do the change & bounce the resource which requires the dependency resources to be bounced as well. In case you don't want to stop the database synchronization remove the dependency then after the change add the dependency back (AOAGres - VCO - IP).
RegisterAllProvidersIP is to 1 for multi-subnet setups and is advised to be used along with TTL
Import-Module FailoverClusters
Get-ClusterResource
Get-ClusterResource yourListenerName | Set-ClusterParameter RegisterAllProvidersIP 0
Get-ClusterResource yourListenerName | Set-ClusterParameter HostRecordTTL 300
Stop-ClusterResource yourListenerName
Start-ClusterResource yourListenerName
Make sure you cross verify the dependency chain before & after this activity.
And in case of resource recreation outside of SQL Sever, add the port# from SSMS.
This public URL can help with guidance.
https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/create-or-configure-an-availability-group-listener-sql-server?view=sql-server-ver16
https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/create-or-configure-an-availability-group-listener-sql-server?view=sql-server-ver16