Re: SA Security
- From: "Jasper Smith" <jasper_smith9@xxxxxxxxxxx>
- Date: Mon, 24 Apr 2006 23:05:56 +0100
You can allow them to see jobs (definition and history) by adding them to
the TargetServersRole in the msdb database. They will not be able to see
whether a job is currently running or not though (although there is a
convoluted way to do that by querying sysprocesses) and they can't modify or
start job jobs they don't own
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Ken Widner" <KenWidner@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:95CA5197-DD6F-4AEE-BA9C-BFE10FDE8C7B@xxxxxxxxxxxxxxxx
Is there a way to give someone in SQL 2000 that isn't an SA the ability to
see jobs when their not the owns of those jobs. Someone told me about
making
a change to one of the Sp's in msdb that would fool the system into things
your in an SA role when your really not. Anyone know anything about
this.?
.
- Prev by Date: Re: public role question
- Next by Date: Re: Assigning Permissions to a Database
- Previous by thread: event ID for windows (trusted) authentication and failed ones as well?
- Next by thread: How to hide unauthorized databases with SQL 2005?
- Index(es):
Relevant Pages
|
|
