RE: sql tasks

Yes; that is the owner of the job is the context it runs under. When you
create a job or maintenance plan it goes under your name by default.

So when doing that unless your access has access to the server; the job will
fail because the owner is set to you whether you execute it manually or
automatic (at least that's what I remember happening few months ago with me
heh ^^).

--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCITP: Database Administrator
MCTS: SQL Server 2005
http://sqllearnings.blogspot.com/


"Reeves" wrote:

Mohit,

Thanks for the response, and one more note: will sql jobs (sorry for the
confusion) run under the same context (account) no matter how they are
spawned?

So do they both run under the same context if they are run manually or
scheduled?

Reeves.

"Mohit K. Gupta" wrote:

By task you mean SQL Server JOB?

The job will run under the account of the owner on SQL Level and on OS Level
it will use SQL Server Service/Agent Service account unless you have proxy
account set up. It

--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCITP: Database Administrator
MCTS: SQL Server 2005
http://sqllearnings.blogspot.com/


"Reeves" wrote:

When a user logs onto a box to manually run a task, is the task run under the
context of the user or the SQL Agent service?

1) Joeuser logs in and manually runs a task

vs

2) SQL Agent runs a scheduled task

Thanks
Reeves
.

Relevant Pages

  • RE: sql tasks
    ... confusion) run under the same context no matter how they are ... "Mohit K. Gupta" wrote: ... The job will run under the account of the owner on SQL Level and on OS Level ...
    (microsoft.public.sqlserver.security)
  • running job without being the owner?
    ... SQL 2000 ... Is that possible without making a user the owner of job, ... The account is not an SA eaither. ...
    (microsoft.public.sqlserver.programming)
  • Re: What queried should I use???
    ... Is there a better way to write the SQL ... account number in the Union query every time. ... What's the context? ... maybe we can find way to automate the process of ...
    (microsoft.public.access.queries)
  • Re: Missing table
    ... execute the commands within Query Analyzer. ... The first piece of sql displays the table owner, type, and the name of the table. ...
    (microsoft.public.sqlserver.server)
  • Re: Encryption key storage
    ... I have a few questions about my options to store encryption keys. ... values so we don't need to do an LDAP call for each individual session ... dispersed through SQL Reference and Supplied PL/SQL Packages ... SQL> create or replace context myctx using scott.setctx accessed ...
    (comp.databases.oracle.misc)