Service Acct change on a Cluster Server

  • Hi, Is there a best practice that MS recommends when changing SQL Server Service acct on a cluster server. I changed the service acct first and then took the service offline and then brought it on line and it works just fine. But I just want to get you guy opinion incase i need to take Services offline first and then change the acct and bring it online. comments are appreciated

    Thanks

    Shas3

  • I can't say for definate but I've fairly sure that I've read an article recently saying you should change the account via Enterprise manager (I think it was related to full-text permissions and potential problems if done via the normal services mmc).

    Found it.....

    http://support.microsoft.com/default.aspx?scid=KB;EN-US;277549

    My thinking is that if Full-Text population relies on the account being changed via this method then maybe something else does too.

    Hope this helped

  • This doesn't applies to me since I am not using Full Text. I appreciate your reply

    Thanks

    Shas3

  • I recently got a book entitled "Microsoft SQL Server 2000 High Availability" and in Chapter 6 for failover clustering it says to make the changes in Enterprise Manager.  It's a great book and even gives step-by-step instructions for most questions on Clustering, Log Shipping, & Replication.  I've gotten lots of good tips from it (Kimberly Tripp is one of the authors).

    Linda

  • The reason microsoft prefers making changes in the Enterprise manager is that it does update the services on both nodes. If you do it through Services snap-in, you will have to manually change the service account on both nodes.

  • I have read the recommendations somewhere that if you really had to change accounts in Services applet for example to be able to start services at all you still need to go into Enterprise Manager after that and reset the account there. I am not sure where I read it, it was long time ago but the exlanation was that when you do it from EM it also sets appropriate file permissions and registry entries. It also assigns Windows user rights to this account. This recommendation is more important if your SQL Startup account does not have full administrative rights and full file system access.

    For example MCSE Training Kit for SQL Server 2000 Administration says:

    "........Finally, changing the SQL Server or SQL Server Agent service account after setup must be done properly, or you might have NTFS permissions problems or Windows registry permissions problems........If you want to change the service account used by the SQL Server or SQL Server Agent services after setup, you must use SQL Server Enterprise Manager to ensure the proper functioning of these SQL Server services and SQL Server 2000...."

    Yelena

    Regards,Yelena Varsha

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply