April 1, 2020 at 6:37 pm
Hi,
We have some of the SQL Server AlwaysOn environment (NonPROD) where we do not require alwayson any longer. Instead a standalone system will be sufficient. Without provisioning a new environment (standalone), how we can use the existing HA to a standalone and remove one of the other nodes? Does Microsoft has any clearly defined document? Did anyone try this approach? Our SQL Servers are on AWS EC2
Thanks.
April 1, 2020 at 7:12 pm
You can remove the availability groups - https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/remove-an-availability-group-sql-server?view=sql-server-ver15
You can just also remove the other node and let it run single node.
April 1, 2020 at 8:04 pm
Hi Steve,
Do you think there may be any issue in future if we would like to patch the instance? Also do we have any clear steps about how to disassociate the cluster from the SQL HA so that the binding can be removed easily from between HA and Cluster?
Regards
Thanks.
April 1, 2020 at 8:11 pm
There shouldn't be patching issues. You won't have HA, so patching this is the same as other systems. There are people that always install SQL as a single node cluster, just in case they decided to add a second one later.
There isn't a cluster by default for an AG. Do you have an FCI here as well?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply