SQL Server and Agent Accounts



Hi guys - I have two questions about accounts that sql server services
run under:

1) When I try to install the publisher, it fails to create the
distribution database because it says that login failed for NT
Authority\System (the SQL Server service was running as Local System). When
I added NT Authority\System (as sysadmin), everything worked fine. Then I
removed it and assigned a windows account to SQLServer service that was a
sysadmin, and it also worked fine. So my question is, why does SQLServer
service need to be running under an account that is a sysadmin?

2) I have create a merge replication with pull subscriptions. I noticed
that the SQL Agent can run under an account that is not in the publisher. So
when I synchronize does it use the account that is currently logged in?

Thank you for your help,
Maer


.



Relevant Pages

  • RE: Best way for a SQL Server Service to Log On to the Local Computer
    ... user account for your SQL Server services since trusted security can be ... packages etc may need more permissions (sysadmin or local administrator). ... It is always our pleasure to be of assistance. ...
    (microsoft.public.sqlserver.security)
  • sql server services
    ... all of the sql server services are running as 'Local System' account. ...
    (microsoft.public.sqlserver.security)
  • Re: donain account for SQL services -- required to have an email mailbox??
    ... various SQL Server services. ... Should it have an email mailbox?? ... We don't use these domain accounts for anything else. ... The account should not have a mailbox. ...
    (microsoft.public.sqlserver.server)
  • Re: sql server services
    ... all of the sql server services are running as 'Local System' account. ... other services such as Exchange will not be able to communicate. ...
    (microsoft.public.sqlserver.security)
  • Jobs, owners, and permissions
    ... When the owner of a job is not member of sysadmin, ... must configure a proxy account in order to execute ActiveX ...
    (microsoft.public.sqlserver.security)

Loading