Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Gary T
Starting Member
1 Post |
 Posted - 2003-01-28 : 04:24:03
|
| Hello,All our SQL Server Agent Jobs are owned by sa. When there is an application problem we would like our developers to be able to log in to SQL Server under a troubleshooting account and be able to view the success (or failure) of these jobs.Is there anyway that we can enable an account for them that would enable them to do this without making that account sa? Or Im wasting my time looking for a solution?Thanks,Gary. |
|
|
rihardh
Constraint Violating Yak Guru
307 Posts |
Posted - 2003-01-28 : 04:59:10
|
Quote from BOL:quote:
Anyone can create a job, but a job can be edited only by its owner or members of the sysadmin role.
|
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-01-28 : 12:18:27
|
| You might be able to just give them the select privileges on the msdb..sysjobhistory table. I wouldn't do it, but it probably would work. |
|
|
|
Revuca
Starting Member
19 Posts |
Posted - 2003-01-29 : 05:04:30
|
| Quote from a MS book : (it's probably more than you need, but it might be what you're looking for.)By default, jobs are owned by the creator of the job and operate in the security context of that login, regardless of who executes the job. Members of the sysadmin server role can assign ownership to any valid login. Ownership of a job does not grant the right to execute any particular job step. Permission to execute each Transact-SQL job step is verified by the SQL Server service using permissions granted within SQL Server. By default, permission to execute CmdExec and ActiveX job steps is granted only to jobs owned by members of the sysadmin server role. These job steps run in the security context of the SQL Server Agent service account. Permission to run CmdExec and ActiveX scripting job steps can be granted to users who are not members of the sysadmin fixed server role. These job steps owned by non-sysadmins run in the security context of a specified Windows account called a proxy account and inherit the rights granted to that account. To configure the proxy account in SQL Server Enterprise Manager, expand the Management container in the instance, right-click SQL Server Agent, and then click Properties. In the SQL Server Agent Properties dialog box, click the Job System tab. When you clear the check box in the Non-SysAdmin Job Step Proxy Account group box, the SQL Agent Proxy Account dialog box appears so that you can then configure the proxy account. hthMikeEdited by - revuca on 01/29/2003 05:06:34 |
|
|
|
|
|
|
|
|
Viewing SQL Server Agent Jobs