Article ID: 239885 - View products that this article applies to.
This article was previously published under Q239885
This article describes the steps to change the service startup accounts for a clustered computer that is running Microsoft SQL Server.
SQL Server 6.5 and 7.0Warning If you try to change service account information, such as the account name or the password, while SQL Server is clustered, the service cannot start when you try to bring the cluster group online. In this scenario, you may have to manually remove SQL Server completely from both nodes, secure your SQL Server databases, and then reinstall SQL Server.
To change the service startup accounts for a clustered computer that is running SQL Server, follow these steps:
SQL Server 2000Although the account that is used is automatically assigned the appropriate privileges during the installation process, if the account is changed, it (or the Administrator group) must have the following attributes:
If you do not use SQL Server Enterprise Manager to change passwords, full-text search may not function properly, and SQL Server may not start.
If you are using Kerberos Security Support Provider Interface (SSPI) authentication in a Microsoft SQL Server 2000 and Microsoft Windows 2000 environment, you must drop your old service principal name (SPN), and then create a new one by using the new account information. See the "Security Account Delegation" topic in SQL Server 2000 Books Online for details about using SETSPN to do this.
Article ID: 239885 - Last Review: August 16, 2006 - Revision: 6.7
Contact us for more help