We migrated many instances of SQL Server 2008/R2 on Windows 2008R2 and 2012 on Windows 2012 to newer Windows 2016 with SQL Server 2014 and 2016 versions.

The old clusters were configured with either 2, 3, or 4 nodes.

Now to begin with cleaning up and decoming the Windows 2008R2 and 2012 servers, we would need to:

  1. For 2 node clusters, uninstall SQL Server when there is no activity.

  2. For the with 3/4 node clusters, we have one node active since application jobs are still running (just the SQL Server agent jobs running ssis packages which are already connecting to the new cluster). The migration of these jobs will take time, however. Hence I am looking for a way to break the cluster or uninstall SQL Server from the non-active nodes that will ensure the jobs continue to run on the active node.

What is the safest way to clean up the SQL Server clusters and make sure they do not break in a scenario where a single node of the 3-4 nodes needs to remain active?

Appreciate if there is any checklist one follows and can share while bringing down the SQL Server cluster.

  • 2
    Can you add detail on "3-4 node where one of the node is still live and is needed but not with SQL"? – David Browne - Microsoft Oct 9 '18 at 13:43
  • Also let me know how you migrated to new cluster, was it add new node to current WSFC, then add node to SQL Server FCI and then later failover to new nodes ? – Shanky Oct 9 '18 at 15:26
  • @Shanky- It was completely a new installation of windows cluster followed by SQL clustering as we moved from Wk208 to Wk2012 – BeginnerDBA Oct 9 '18 at 17:32
  • @DavidBrowne-Microsoft: Updated my question – BeginnerDBA Oct 9 '18 at 17:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.