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

I recently was asked to bring a new SQL server online. Having no experience with this I of course did quite a bit of research on best practices. The install went without any issues with the exception of the following:

Per:Reference (Many other sources sited the same practice)

I installed MSSQL Server with a domain service accounts for both the agent and db service. Both services start correctly upon boot. I setup alerts and decided to test them. Upon killing the sqlservr.exe through task manager, the agent fails to restart the service.

Reviewing the logs I found this error:

[368] AutoRestart: Unable to restart the MSSQLSERVER service (reason: Access is denied)

Upon failing to restart 3 times, the SQL Agent itself shuts down.

The service users have no admin rights, but from my research SQL 2008 R2 is designed to run least privileged. I'm would really like to avoid giving the agent local admin rights.

I assumed(I know) the SQL installer did some magic to make this work upon install.

The best idea of a solution so far is to modify the SDDL outlined here

Any advise would be appreciated.


SQL Server 2008 R2 Standard MS Win2k8R2 Datacenter SP1

share|improve this question

Make sure the user has ownership of the database files themselves.

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.