Re: Am I doing this right?
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Thu, 18 May 2006 19:17:50 -0600
A deny for a sysadmin won't do anything. Members of the
sysadmin role bypass security checks - sysadmins are able to
do anything on the server and in any databases.
-Sue
On Thu, 18 May 2006 11:41:03 -0700, Steve
<Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have a new user that will eventually be another admin on our SQL Server 200
installation. I want to give him permission to stop and Restart Scheduled
jobs, yet not have permission to insert/update or delete in specific
databases until he gets more experience. The only predefined server role
that allows access to scheduled jobs is SystemAdministrator, but that also
gives permissions everywhere to everything.
Will creating a User in each database I want to protect based on his login,
and then selecting db_denydatawriter do what I want to do, or will the also
selected SystemAdministrator priviledge override this altogether?
.
- Prev by Date: Re: Encrypting data in SQL 2005
- Next by Date: Re: SQL 2005 user not having permissions to write a file in a folder
- Previous by thread: Windows authentication to sql server 2000 question
- Next by thread: Re: Am I doing this right?
- Index(es):
Relevant Pages
|
|
