locked
changing domains for an existing SQL Server 2005 Failover Cluster RRS feed

  • Question

  • Hello All,

    Appreciate your support regarding this subject “changing domains for an existing SQL Server 2005 Failover Cluster"

     

     


    Volcano "DATA is the Focus, Business is the Target”"
    Thursday, April 15, 2010 5:30 PM

Answers

All replies

  • Hello,

     

    Please see section “How to change domain group for a clustered service” on the following article:

    http://support.microsoft.com/default.aspx/kb/915846?p=1

    Please read the following articles also:

    How to move a Windows Server cluster from one domain to another
    http://support.microsoft.com/kb/269196

    http://support.microsoft.com/kb/244980

    You may find useful the following threads:

    http://social.msdn.microsoft.com/Forums/en-US/sqlsecurity/thread/53c95f94-ecb7-4e6c-a5b8-43f6d0c2bedd

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Thursday, April 15, 2010 10:59 PM
  • thanks for your reply

    I found this artical How to change domains for a SQL Server 2000 failover clusterhttp://support.microsoft.com/kb/319016 is this the same way I should follow for SQL Server 2005 .

    I checked the section you mentioned above “How to change domain group for a clustered service” is this the only steps I need to change the domain

    finall question Do I need to change the domain for windows first before change SQL Server cluster Domain

     

    appricaite your support


    Volcano "DATA is the Focus, Business is the Target”"
    Thursday, April 15, 2010 11:48 PM
  • Hello,

    KB319016 is just for SQL Server 2000.

    I would say, move the Windows Server cluster first, then log into your cluster nodes while the virtual server is offline, and change service account/domain group using SQL Server Configuration Manager.

    If you are planning to change IP address, don’t forget the following article:

    http://support.microsoft.com/kb/244980

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Friday, April 16, 2010 3:45 AM
  • Hello,

    KB319016 is just for SQL Server 2000.

    I would say, move the Windows Server cluster first, then log into your cluster nodes while the virtual server is offline, and change service account/domain group using SQL Server Configuration Manager.

    If you are planning to change IP address, don’t forget the following article:

    http://support.microsoft.com/kb/244980

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Friday, April 16, 2010 3:46 AM
  • Sorry ,, I can't get your point . the only step I need is change the SQl Server services account\domain from configuration manger while virtual server resources offline !!!! please confirm.

     

     


    Volcano "DATA is the Focus, Business is the Target”"
    Friday, April 16, 2010 12:26 PM
  • Hello,

    This is a tricky process. Some guys would prefer to rebuild the whole cluster from scratch, including me. In fact KB269196 says “We do not recommend performing this type of move in a production environment.”

    However, based on the articles I posted above, the procedure should be the following:

    1.   Stop SQL Server services

    2.   Move the cluster from one domain to another using KB269196. After rejoin each node, re-create virtual server name and cluster name if needed (AD/DNS)

    3.   Use KB915846 to change domain group/service account for the clustered services. As you can see in this KB, is not an easy process.

    If you prefer, you can validate this process calling Microsoft Support. Maybe they can tell you if there is something missing.

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Friday, April 16, 2010 2:15 PM
  • thanks for your valuable info.

    which part you mean is tricky ,, windows part or the sql part or both as I will only implement the SQl part :)


    Volcano "DATA is the Focus, Business is the Target”"

    Friday, April 16, 2010 11:26 PM
  • Hello,

    I was thinking about things that could possible happen on different scenarios.

    Not much documentation about this subject.

    I wish you success. Have fun.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Saturday, April 17, 2010 3:48 AM
  • This is Just to tell you I followed another method which Is.

    • Backup all SQL Server Objects.
    • Uninstall SQl Server
    • Change the Windows Domain
    • Install SQl Server 2005 bason on the new Domain

    thanks for ur support ;)


    Volcano "DATA is the Focus, Business is the Target”"
    Saturday, May 1, 2010 6:51 PM
  • Hello,

    Thank you for your feedback. It could help others in the future.

    Regards,

    Alberto Morillo

    Saturday, May 1, 2010 8:26 PM