Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4689

Removing Always On and leaving standalone SQL instance? (SQL 2014 Always On)

$
0
0

I've got a 2 node SQL Server Environment that was setup as always on. (Windows 2012R2/SQL 2014). I have removed all the databases that were part of the always on group, deleted the AOAG listener, and deleted the AOAG group.

My question is this..

One of the nodes in the AOAG environment has some databases just on that specific node (not part of the AOAG).  Is there a way for me to break down the cluster and get rid of everything but still keep the standalone SQL running on one of the nodes with the databases that were on it?

As an example - let's say my environment looks like this:

SQLNODEA

SQLNODEB

SQLAOAGLISTENER (the AOAG LISTENER)

I've deleted the listener and AOAG above, but I still have some databases JUST served directly off SQLNODEA. 

How can I get rid of the Windows clustering stuff but still keep SQLNODEA?  Can I evict SQLNODEA from the cluster and let it run standalone?  Then delete/shutdown SQLNODEB as it's no longer needed?

I remember in the past with SQL Shared storage clusters that there was no way to get rid of the cluster without uninstalling SQL, but I thought that might not be applicable to Always on since each server is it's own SQL installation?  I have a couple of applications pointed directly at the SQL instance on SQLNODEA and ideally I'd like to keep that server running by itself, and shutdown/get rid of SQLNODEB

Thanks for any help!

-Dave


Viewing all articles
Browse latest Browse all 4689

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>