We have a SQL database server that has multiple databases running under a
single instance. Each database has a dedicated group of users and admins.
Each database has a dedicated set of maintenance jobs (created by a
maintenance plan) and custom jobs created to perform time critical task. What
I want to do is secure the execution of SQL Agent jobs to prevent user/admins
from other databases running the wrong agent job. I had a case where an admin
from database “A” accidentally ran a SQL Agent Job from database “B”. The
admins in question don’t have “SA” rights but have DBO rights to only their
database. The server login security prevents them from see the other
databases in enterprise manager but they can see all SQL Agent jobs and they
can run them.

Signature
Kurt Moskal
John Bell - 27 Feb 2005 12:17 GMT
Hi Kurt
From BOL:
A user who can execute sp_start_job 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.
This does not tie in with your experience, therefore you may have a
ownership/permissions problem.
John
> We have a SQL database server that has multiple databases running under a
> single instance. Each database has a dedicated group of users and admins.
[quoted text clipped - 12 lines]
> they
> can run them.