SQL SERVER – Changing Cluster Domains with WSFC and SQL FCI Support Limits

To Move SQL Server Cluster installations between domains, I plan an application-specific migration. The Windows cluster capability alone does not establish SQL support.

Intact cases remain in an existing frame beside a prepared target frame and a separate staging bench.

The reader used SQL Server 2014 on Windows Server 2012 after an acquisition. Their standalone-server domain-change guide didn’t cover the cluster. I recommended a prepared target, backup/restore and recreated instance objects. The team later hired me for performance tuning.

Windows Server 2019 added cluster domain-migration capabilities. That doesn’t establish support for every clustered application. SQL Server FCI documentation still requires uninstalling and reinstalling its failover cluster components for a domain change.

Inventory service identities, SQL logins and SIDs, SPNs, cluster network names, DNS, certificates, storage access, jobs and dependent applications. Rehearse backup restore and failover on the intended destination, and retain a tested rollback path. A Windows cluster migration wizard does not copy database data for you.

Treat the Windows version, SQL Server version and clustered role as separate compatibility questions. Don’t execute domain, account or cluster changes from a short generic checklist.

Related reading

A Windows cluster capability is not SQL Server application support, it is one part of the migration requirements.

Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.


Discover more from SQL Authority with Pinal Dave

Subscribe to get the latest posts sent to your email.

SQL Domain Controller, SQL Server, SQL Server Cluster
Previous Post
SQL SERVER – AlwaysOn Availability Group Listener – This TCP Port is Already in Use
Next Post
SQL SERVER – The Cluster Resource ‘SQL Server’ Could Not be Brought Online Due to an Error Bringing the Dependency Resource

Related Posts

2 Comments. Leave new

  • Siddharth Verma
    March 3, 2018 10:45 am

    At my earlier client.. We moved multiple sql clusters from one domain to another domain [due to merger/acquisition] without installing a new Cluster in 2nd domain and doing traditional backup/restore. We knew it is not recommended/supported by microsoft, so we first tested it in a less critical cluster environment and documented all the lessons learnt, then accordingly decided our approach/action plan for other more critical clusters. Best part, we could successfully do it. :)

    Reply
    • As long as you are aware of the risks involved and don’t want any support from Microsoft then its perfectly fine. Doing homework is very important, which you have already done. If you wish, please share what you have learned. This would help other readers.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.