TIP - How to change the startup account in SQL 2005?

  • Article

Generally, you would set the startup accounts for SQL Server services during the startup.

However, there are times when you might want to change it after installation.

Many DBAs are so used to Services.msc console that they use it to change the startup account of SQL Server 2005 or 2000 services as well.

But this is NOT a healthy practice. You should change the startup account of SQL Server services ONLY through SQL Server Configuration Manager in SQL 2005 and SQL Server Enterprise Edition in SQL 2000.

Reason?

The startup account for each SQL Server service needs to be granted:

- Certain Windows Privileges (like log on as a service etc.)

- Adequate permissions on the SQL Server registry keys

- Permissions on the SQL Server folders on the file system

When you specify the startup account during setup, the setup program grants these takes care of the above. However, if you change the startup account through services.msc, then these activities cannot be performed and you could very well end up with a broken SQL Server installation.

To learn how to change the startup accounts through Configuration Manager, refer to https://msdn2.microsoft.com/en-US/library/ms345578.aspx

 

In case you decide NOT to use SQL Server Configuration Manager or Enterprise Manager, you can still follow the steps to grant all privileges and permissions by following this KB article https://support.microsoft.com/?id=283811

 

UPDATE - Special considerations for SQL Server 2005 Clusters

If you decide to change the startup account of SQL Server services on a cluster, you should do the following:

  • Add the new account under the domain group in Active Directory. For example, if you want to change the startup account of SQL Server Agent on the cluster, you should add the new startup account to the SQL Server Agent domain groups in your AD.
  • Change the startup account on the active node of the cluster using Configuration Manager.

To know more, refer to KB 239885 and KB 915846. 

 

Hope this helps to consolidate the information in one place for you.