In the enviornment I'm currently working in, a few (non DBA) teams have various SQL Agent jobs that they are responsible for the management of. They frequently need to update jobs steps or schedules, run jobs, view history...etc. When the teams are in SQLAgentOperatorRole they can do most of the things that they need to apart from editing the jobs. To get round this we have setup a SQL login that owns the jobs the manage and they open a seperate connection using this login to edit the jobs. The only other way to allow this functionaility that I could think of was to give them sysadmin & I'm not prepared to give this permission out to non DBA's.If a job could be owned by a Windows group (i.e. the non DBA teams group), then they could edit their own jobs without requiring the SQL login (& seperate connection) or sysadmin membership
Category