From: kob uki (kob_uki_at_hotmail.com)
Date: Mon, 7 Jul 2003 10:25:31 -0600
Yeah, I have modified the call according to the article, but it is still not
clear to me WHY it is so.
"By design" doesn't help too much. :) The link is impersonating, the job is
owned by a sql server user (not windows authenticated one), the job is
invoked by one windows\user1 and the job's step gets executed under the
credentials of yet another windows\user2. SQL Server can not perform SETUSER
Another thing: osql -E -Q "exec my_sp"
returns successfull execution if my_sp doesn't exist.
"VUILLERMET Jacques" <email@example.com> wrote in message
> It's by design.
> See : PRB: SQL Server Agent Job Fails When the Job Uses a Linked Server
> the Job Owner Is Not a System Administrator
> "kob uki" <firstname.lastname@example.org> a écrit dans le message de news:
> > I have an openquery select statement to a linked server.
> > A job (having this openquery) is successful only if the owner of the job
> > a sysadmin. This is nuts. I mean, should it be this way?
> > The openquery runs fine from QA even if the user is not sysadmin.
> > The error of the job is Remote access not allowed for Windows NT user
> > activated by SETUSER. [SQLSTATE 42000] (Error 7410).
> > So, if the the owner of the job is sysadmin then there is no SETUSER,
> > it is not then SETUSER... not clear. (no proxy user defined).
> > Can anyone explain this?
> > Thanks,
> > kob_uki