June 25, 2013 at 9:24 pm
For all DBA's
Currently, I have sysadmin rights on our SQL Server 2008R2/2012. My DBA are now implementing policy where they will remove our sysadmin rights, which we are fine with it.
The problem is we are not able to modify/update each other SQL Agent jobs after they lower our rights. With sysadmin rights we can alter anyone's job since we are very small team.
How can we accomplish this task after they remove our sysadmin rights? Since we are backup for each other we do need to have flexibility where we can modify each other job in a such a event....
On side note, our DBAs are not responsible for scheduling or maintaining jobs.
please advise.
July 1, 2013 at 1:35 pm
This recent thread goes through it in pretty good detail.
http://www.sqlservercentral.com/Forums/Topic1438841-1526-1.aspx
Microsoft could do a better job exposing SQL Agent functionality to non-sysadmins by making some things possible while blocking others (i.e. making it more granular) but at present it is not surprising that non-sysadmins cannot manage other people's jobs. If you, as a non-sysadmin, can schedule a job to run with a job owner of sa (regardless of whether the Login is disabled) or any other Login in the sysadmin Role you can easily make yourself a sysadmin and take over the database instance in very short order.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply