Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


We are a smallish company that prefers to keep things simple and not have to manage our Active Directory very much. My company uses a single administrator account to setup and do all the admin stuff that needs to be done. Recently we changed the password on that account and our MSSQL 2008 R2 server stopped working. We found out the issue was that the service related to the MSSQL server was setup to be started and run by the administrator account that was using the old cached password. We changed the password and it started working again.

Related fix for our issue:

My Question:

Should the account used to start the MSSQL service be a domain user account setup in a particular fashion or is ok to select a local account like Network Service or Local System.

share|improve this question
up vote 2 down vote accepted

In general, SQL Server should not be run as Domain Admin or any administrative user. Some administrators do run SQL Server as domain admin, so they do not have to register SPN's manually. See for discussion on what account to use in lieu of the Domain Admin.

My personal preference is a Domain User account, so that you can still grant permissions on backup shares and other network resources that may be accessed by the Server, but that is by no means a universal reccomendation.

See for details on registering SPNs so that Kerberos Authentication will work without Domain Admin privelages.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.