Re: Seeing Jobs in 2000
- From: "Russell Fields" <russellfields@xxxxxxxxxx>
- Date: Mon, 3 Dec 2007 12:10:17 -0500
CLM,
On SS2000, you can place the operators in the TargetServersRole of the msdb
database. This will allow them to view all job statuses, etc. However,
membership in that role would prevent them from being able to create a job.
(In case that is important, then they might need two logins: 1 - create
jobs, 2 - see all jobs.)
This is a side-effect of this role and was not its purpose. In 2005 there
are specific new roles for this and other levels of msdb access.
RLF
"CLM" <CLM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:57B09DDF-C627-49F6-B15A-4159CC51C791@xxxxxxxxxxxxxxxx
Our goal is to let the operators see the jobs in Enterprise Manager (SS
2000). We specifically want them to see the Status column so that they
know
they state of a job, i.e. whether it is complete or running and, if so,
what
step it is on. I tried to create a login and then went into Profiler to
see
what system stored procs came up when I clicked in the Jobs part of Ent
Mgr.
I then looked up all the stored procs and gave this login execute
permission.
I also gave them read permission in msdb.
But to make a long story short, I cannot get that Status column to read.
And, besides that, there has got to be an easier way! How can I
accomplish
this without giving them sa or dbo?
.
- Prev by Date: Re: Encryption in SQL Server 2005.
- Next by Date: db_owner
- Previous by thread: Re: Encryption in SQL Server 2005.
- Next by thread: db_owner
- Index(es):
Relevant Pages
|
