RE: Unable to set the SQL Agent proxy account

From: Kevin McDonnell [MSFT] (kevmc_at_online.microsoft.com)
Date: 12/11/03 

Date: Thu, 11 Dec 2003 21:33:58 GMT

Not a good idea. The Proxy Account should not be the same account used to
Start SQL Server and SQL Agent. It should be a domain account with minimal
privledges.

SQL Server Agent proxy accounts allow SQL Server users who do not belong to
the sysadmin fixed server role to execute xp_cmdshell commands and to own
SQL Server Agent jobs. The administrators can assign appropriate security
permissions to the proxy account to control the ability of these jobs to
access resources in the network.

Thanks,

Kevin McDonnell
Microsoft Corporation

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

Relevant Pages

  • Re: SQL Server Agent Proxy Account / XP_CMDSHELL
    ... The proxy account is unrelated to SQL Server object permissions. ... must have xp_cmdshell execute permissions when xp_cmdshell executed ... execute permissions on xp_cmdshell. ...
    (microsoft.public.sqlserver.security)
  • Re: Cscript from a SQL Stored Procedure?
    ... You may want to check the proxy account. ... >that uses SQL SERVER 2000 as it's database. ... >Basically we are trying to add code that calls the .vbs script so that when ... >doesn't seem to execute. ...
    (microsoft.public.sqlserver.server)
  • RE: Import Warning Message
    ... I had the same problem when I set up a proxy account to use the ssis service ... My Source DB is on a hosted remote sql server 2005. ... Warning 0x80049304: Data Flow Task 1: Warning: Could not open global shared ...
    (microsoft.public.sqlserver.dts)
  • Re: VB 6, SQL Server 2000, xp_cmdshell
    ... server role named "sysadmin". ... You need to understand what the SQL Server service role "sysadmin" is. ... If the login who owns the job isn't sysadmin, then the proxy account is used. ... then ensure that that id has access rights to ...
    (microsoft.public.sqlserver.server)
  • Re: Autostart MS Agent on Win98/Me
    ... If you really rely on SQL Server Agent being started and you have not a lot ... > with Entreprise manager and the agent start with WinNT... ... I can manually start the agent with the MSDE service manager, ...
    (microsoft.public.sqlserver.msde)