How can a non-owner start a job?
From: Andrew Drake (andrewdrake_at_hotmail.com)
Date: 07/17/03
- Next message: Peter Thelin: "Re: Encryption to and ADP"
- Previous message: Tariq: "Protecting my database"
- Next in thread: Russell Fields: "Re: How can a non-owner start a job?"
- Reply: Russell Fields: "Re: How can a non-owner start a job?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 17 Jul 2003 12:19:37 +0200
Hi!
We've encountered the following problem:
There is a DTS package scheduled for execution every night as a SQL Server
Agent Job. Both DTS package and Job are owned by a user who is a member of
the sysadmin role. And it works fine.
However, from time to time it is required to run the DTS package (or - what
is equivalent - the job) immediately , and it should be done by a user who
is not the owner of the job.
So it raises the question: How can a non-owner start a job?
MSDN states for sp_start_job:
"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."
The user who is intended to start the job is not and will be not a sysadmin.
Is there any workaround to this problem?
Many TIA,
Andrew
- Next message: Peter Thelin: "Re: Encryption to and ADP"
- Previous message: Tariq: "Protecting my database"
- Next in thread: Russell Fields: "Re: How can a non-owner start a job?"
- Reply: Russell Fields: "Re: How can a non-owner start a job?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|