Re: Windows Group Access to SQL Scheduled Tasks - SQL 2000
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Thu, 19 Oct 2006 21:01:01 -0600
Keep in mind, going that route isn't documented and isn't
supported. The permissions for TargetServersRole have
changed in service packs.
-Sue
On Thu, 19 Oct 2006 08:02:03 -0700, SteveT
<SteveT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Thanks Sue for leading me in that direction. (and for reading my lengthy
explanation)
I experimented with the TargetServersRole in msdb, and indeed found that
adding my Windows group as a member allowed full enumeration of the SQL jobs.
But I also found degradated functionality since it appears that this role by
default "denies" access on several key procs. While not recommended, I went
and cleared the the "deny" parmissions on these objects, and now I get the
complete functionality I was looking for. This membership plus exec access
on several procs allows the target users full access (read and update) to all
jobs. In fact, when a target user changes an attribute in a job, the owner
is implicitly changed to this user, while the actual owner field in the job
remains "greyed out".
So it looks like I've found a workable solution. Thanks again!
.
- References:
- Re: Windows Group Access to SQL Scheduled Tasks - SQL 2000
- From: Sue Hoegemeier
- Re: Windows Group Access to SQL Scheduled Tasks - SQL 2000
- From: SteveT
- Re: Windows Group Access to SQL Scheduled Tasks - SQL 2000
- Prev by Date: Viewing effective Permissions by Role VS by Table
- Next by Date: Re: SQL to get a list of users/roles/permissions
- Previous by thread: Re: Windows Group Access to SQL Scheduled Tasks - SQL 2000
- Next by thread: Viewing effective Permissions by Role VS by Table
- Index(es):
Relevant Pages
|
|
