According to BOL these are the rules for sp_start_job
Permissions
Execute permissions default to the public role in the msdb database. A user
who can execute this procedure and is a member of the sysadmin fixed role
can start any job. A user who is not a member of the sysadmin role can use
sp_start_job to start only the jobs he/she owns.
When sp_start_job is invoked by a user who is a member of the sysadmin fixed
server role, sp_start_job will be executed under the security context in
which the SQL Server service is running. When the user is not a member of
the sysadmin fixed server role, sp_start_job will impersonate the SQL Server
Agent proxy account, which is specified using xp_sqlagent_proxy_account. If
the proxy account is not available, sp_start_job will fail. This is only
true for Microsoft® Windows NT® 4.0 and Windows 2000. On Windows 9.x, there
is no impersonation and sp_start_job is always executed under the security
context of the Windows 9.x user who started SQL Server.
--
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.allisonmitchell.com - Expert SQL Server Consultancy.
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"MF" <anonymous (AT) discussions (DOT) microsoft.com> wrote
Quote:
I have several DTS packages in Enterprise Manager that are run as jobs in
SQL Server Agent. I want to assign the task of running the jobs to someone
|
who is not a member of the sysadmin role and who is not the owner of the
jobs. How do I do this?