non sysadmin needs to modify a couple of sql agent jobs

Question

non sysadmin needs to modify a couple of sql agent jobs

fizzleme

SSCertifiable

Points: 6906
More actions
February 2, 2009 at 3:35 pm

#94967

We have a contractor who needs to modify a couple of SQl agent jobs on our server. He is using standard SQl security to connect.
The SQL agent jobs are owned by 2 different domain accounts.
I don't want to make him a sysadmin. He currently has read access to a database on the server. In sql 2000 is there any easy way to do this?
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply

Gift Peddie SSC Guru Points: 73570 More actions · Answer 1

I don't think read access can modify SQL Server Agent Job even in 2000 as of SP3a because there is no SP3. The reason SQL Server checks the user write permissions so you may give the person none admin but higher than reader permissions. Check below for what you need from Microsoft because in 2005 the person must be admin or some Agent role or proxy of admin.

http://msdn.microsoft.com/en-us/library/aa213804(SQL.80).aspx

Kind regards,
Gift Peddie

Jeff Moden SSC Guru Points: 1004365 More actions · Answer 2

fizzleme (2/2/2009)
We have a contractor who needs to modify a couple of SQl agent jobs on our server. He is using standard SQl security to connect.
The SQL agent jobs are owned by 2 different domain accounts.
I don't want to make him a sysadmin. He currently has read access to a database on the server. In sql 2000 is there any easy way to do this?

Have the contractor have the DBA do it. Giving the contractor read access to your data is bad enough.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)