SQL Agent Roles

5 Feb 2007 9:37 PM

Michelle

I have a domain account that is assigned the the SQLAgentOperator,
SQLAgentReader, and SQLAgentUser roles. That domain account is able to create
a job and delete the job. But, it is unable to edit the job. If I create a
SQL Login with these same permissions, it is able to edit the job. What am I
missing?

We were looking forward to implementing these new built-in security roles
because we had to use our own security roles to give us similar functionality
in SQL 2000 but it doesn't seem to be working properly in 2005.

Michelle

7 Feb 2007 2:10 AM

Steve

On Feb 5, 1:37 pm, Michelle <Miche***@discussions.microsoft.com>
wrote:

> I have a domain account that is assigned the the SQLAgentOperator,
> SQLAgentReader, and SQLAgentUser roles. That domain account is able to create
> a job and delete the job. But, it is unable to edit the job. If I create a
> SQL Login with these same permissions, it is able to edit the job. What am I
> missing?
>
> We were looking forward to implementing these new built-in security roles
> because we had to use our own security roles to give us similar functionality
> in SQL 2000 but it doesn't seem to be working properly in 2005.
>
> Michelle

not much help for you ...but I just added one of my domain test
accounts as a login to a 2005 server, a user in msdb and a member of
the three roles and that user could add, edit and delete jobs.

7 Feb 2007 2:44 AM

Michelle

Well, thanks for confirming that it DOES work as documented. I wonder if it's
something on our domain? We've had a heck of a time trying to get
trust-delegation set up, too. Not that the two have anything to do with each
other (except the both have the domain in common). Are you running sp1 for
SQL Server 2005? Standard or Enterprise? 64-bit or 32-bit?

I have two domain accounts with the same issue so I don't think that it's
something with that specific account. This is making me frustrated because
guess who gets to deal with any job changes that they need made or who gets
to check to see if their job is running? They can't even see the status.

Argh...

Show quote

"Steve" wrote:

> On Feb 5, 1:37 pm, Michelle <Miche***@discussions.microsoft.com>
> wrote:
> > I have a domain account that is assigned the the SQLAgentOperator,
> > SQLAgentReader, and SQLAgentUser roles. That domain account is able to create
> > a job and delete the job. But, it is unable to edit the job. If I create a
> > SQL Login with these same permissions, it is able to edit the job. What am I
> > missing?
> >
> > We were looking forward to implementing these new built-in security roles
> > because we had to use our own security roles to give us similar functionality
> > in SQL 2000 but it doesn't seem to be working properly in 2005.
> >
> > Michelle
>
> not much help for you ...but I just added one of my domain test
> accounts as a login to a 2005 server, a user in msdb and a member of
> the three roles and that user could add, edit and delete jobs.
>
>