I have a scheduled T-SQL job that I need to run as a different user than
system. I am running into two problems. 1, no matter who the owner is, the
job still runs as system (the SQL Server Agent User). The 2nd part is that
the "run as" is grayed out, so I can't attempt to set the step to run as a
different user.
How can I solve the problem, without changing the user that hte SQL Server
Agent runs as?
Thanks.A job will run under the security context of the SQL Agent
service if the job is owned by a sysadmin. If it's not owned
by a sysadmin, it will run under the security context of the
proxy account. So those are your options.
-Sue
On Tue, 13 Sep 2005 09:12:08 -0400, "Kevin Antel"
<kevina@.cqlcorp.com> wrote:
>I have a scheduled T-SQL job that I need to run as a different user than
>system. I am running into two problems. 1, no matter who the owner is, the
>job still runs as system (the SQL Server Agent User). The 2nd part is that
>the "run as" is grayed out, so I can't attempt to set the step to run as a
>different user.
>How can I solve the problem, without changing the user that hte SQL Server
>Agent runs as?
>Thanks.
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment