Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
proxy account
9 views
Skip to first unread message
Donna
Nov 13, 2002, 11:51:48 AM11/13/02
to
How do I grant a user access to the xp_cmdshell proc
without giving them sysadmin server role permissions? I
found documentation telling me about the
xp_sqlagent_proxy_account proc but no explaination of how
to use it. Does anyone know how this proxy account could
be set up and utilized, or better yet, an alternative way
of giving a user access to the cmdshell without sysadmin
permissions? I'm not even comfortable with a user having
cmd line access. How does everyone else handle this?
without giving them sysadmin server role permissions? I
found documentation telling me about the
xp_sqlagent_proxy_account proc but no explaination of how
to use it. Does anyone know how this proxy account could
be set up and utilized, or better yet, an alternative way
of giving a user access to the cmdshell without sysadmin
permissions? I'm not even comfortable with a user having
cmd line access. How does everyone else handle this?
Sarma UV
Nov 14, 2002, 5:42:04 AM11/14/02
to
Its like any other stored procedure access. Use grant exce
on xp_cmdshell to public / user
on xp_cmdshell to public / user
>.
>
Sue Hoegemeier
Nov 14, 2002, 8:02:28 AM11/14/02
to
Another option is to create a stored procedure that executes
the xp_cmdshell command and if the stored procedure is owned
by dbo and the database is owned by sa, you could grant
permissions on this stored procedure instead of on
xp_cmdshell.
the xp_cmdshell command and if the stored procedure is owned
by dbo and the database is owned by sa, you could grant
permissions on this stored procedure instead of on
xp_cmdshell.
-Sue
Michael
Jan 27, 2017, 10:01:13 AM1/27/17
to
I am getting the below type of error message for all jobs that uses proxy account. These jobs runs fine before with the same proxy account.
Executed as user : Domain\Account.
The process could not be created for step Step Number of job Unique Job ID (reason: A required privilege is not held by the client). The step failed.
I have tried the below resolution with no luck
https://support.microsoft.com/ en-gb/help/911305/sql-server- agent-jobs-may-fail-after-you- change-the-sql-server-agent- service-startup-account-by- using-the-windows-service- control-manager
0 new messages