RE: Starting SQL server services

From: Kevin McDonnell [MSFT] (kevmc_at_online.microsoft.com)
Date: 01/30/04 

Date: Fri, 30 Jan 2004 01:49:45 GMT

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
ol/sql/maintain/security/sp3sec/SP3SEC02.ASP

SQL Server Engine/MSSQLServer
This is the SQL Server database engine and is the only mandatory service.
Run as a Windows domain user account with regular user privileges. Do not
run as local system, local administrator, or domain administrator accounts.
If there are named instances, they will be named MSSQL$InstanceName.

SQL Server Agent Service/SQLServerAgent
This is a support service that allows you to schedule commands and notify
operators when errors occur. Disable if not required in your environment;
otherwise run as a Windows domain user account with regular user
privileges. Do not run as local system, local administrator, or domain
administrator accounts. If there are named instances, they will be named
SQLAgent$InstanceName.

Important SQL Server Agent will need local Windows administrator
privileges if one of the following is true:
SQL Server Agent connects to SQL Server using SQL Server Authentication
(not recommended).
SQL Server Agent uses a multiserver administration master server (MSX)
account that connects using SQL Server Authentication.
SQL Server Agent runs Microsoft ActiveX® script or CmdExec jobs owned by
users who are not members of the sysadmin fixed server role.

Thanks,

Kevin McDonnell
Microsoft Corporation

This posting is provided AS IS with no warranties, and confers no rights.

Relevant Pages

  • Re: Linked Server Connection Error: 18459
    ... Did either of your SQL Server instances run under a domain user account? ... I recommend that you first ensure that your SQL Server ...
    (microsoft.public.sqlserver.connect)
  • Re: Windows authentication/impersonation.. login failed for user null?
    ... You must make sure that domain user account or the domain security group ... ia mapped to a SQL server login/Sql Server ... database user. ... and then make specific SQL Server login as ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Windows authentication/impersonation.. login failed for user null?
    ... You must make sure that domain user account or the domain security group ... ia mapped to a SQL server login/Sql Server ... database user. ... and then make specific SQL Server login as ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Disallow administrator access
    ... Remove the builtin\Administrators from the SQL Server instead of deny. ... "Todd Hazer" wrote in message ... > I have added my domain user account to the security logins and set ... > Jonas Larsen wrote: ...
    (microsoft.public.sqlserver.security)
  • Re: MSSQLServer Service Account
    ... Access and change the SQL Server directory (\Program Files\Microsoft SQL ... a domain user account must be able to read and write ... Member of local Power Users or local Administrators group ... > in order to be able to access the remote server. ...
    (microsoft.public.sqlserver.security)