Is there a way to grant users (non SA's) to view and execute Jobs on
Sql Server 2000 and SQL Server 7 without granting SystemAdministrator
previleges?
Thanks"shub" <shubtech@.gmail.com> wrote in message
news:1139255925.860677.80260@.g43g2000cwa.googlegroups.com...
> Is there a way to grant users (non SA's) to view and execute Jobs on
> Sql Server 2000 and SQL Server 7 without granting SystemAdministrator
> previleges?
> Thanks
>
For multiple users, create a Role, add the users to the Role. Grant the
role all the permissions needed to execute all of the job steps. When you
create the job, set the job's owner = that role.
Rick Sawtell
MCT, MCSD, MCDBA|||adding to ricks answer,
If a user who is not a member of the sysadmin role attempts to run a
job that includes jobs including CmdExec or ActiveScripting then job
steps will fail.
by default sysadmin role can execute CmdExec or Microsoft ActiveX=AE
scripting job steps
In this case you have to set up proxy account using
xp_sqlagent_proxy_account or
right click sql server agent--> properties-->job system-->
Regards
Amish Shah|||And how exactly does one create a role? Is it a server wide role?
(Seems that those can't be changed), or a role in the MSDB database?
Also, it seems impossible to assign a role as an owner:
"[@.owner_login_name =] 'login'
Is the name of the login that owns the job. login is sysname, with a
default of NULL. Only members of the sysadmin fixed server role can
change job ownership."
Any more ideas? I like the solution, but it just doesn't seem to work!
-Sean|||Also, when I try adding a MSDB role as an owner using TSql, I get:
Server: Msg 515, Level 16, State 2, Procedure sp_update_job, Line 217
Cannot insert the value NULL into column 'owner_sid', table
'msdb.dbo.sysjobs'; column does not allow nulls. UPDATE fails.
The statement has been terminated.
Any ideas?
Thanks!
-Sean
No comments:
Post a Comment