Re: Explicit permissions listed twice



Erland Sommarskog <esquel@xxxxxxxxxxxxx> wrote in
news:Xns9A7E7244AFE54Yazorman@xxxxxxxxx:

David Walker (none@xxxxxxxx) writes:
In one of our databases, under Security/Users, when I look at the
Properties for a particular user, and select the Securables page,
each of the permissions is listed twice...

Once with grantor "dbo" and once with grantor "db_owner". The
permissions that were granted by "dbo" do not have Grant, With Grant,
or Deny checked. So, they are kind of empty.

Is this normal? Should I remove the explicit permissions that were
granted by dbo? If so, how? I don't see a way from the GUI in
Management Studio to remove these rows. If they are normal, I won't
worry about them.

I would guess that the granting routine has been run twice. Once by
the real dbo, one by some who has db_owner rights but who were not
dbo.

Removing one set would be a good thingm as there could be confusion
later on when you really want to revoke privilege for a user.

I would create a series of REVOKE statement by selecting from
sys.database_permissions.


OK, thanks. I should be the only one who is granting permissions, but
someone else created the user name. I'll revoke the ones we don't need.
The GUI doesn't seem to have a way. I'm not against using commands (I
frequently do things with commands), but the GUI seems to be fairly
complete in other areas.

David Walker
.



Relevant Pages

  • Problem is w/ .ADP..Re: SQL db Permissions for users not working
    ... You do not have SELECT permissions on the ... SysObjects system table in the database. ... figured out that qualifying the database owner (dbo in my ... >> I feel that the object owner is not dbo, ...
    (microsoft.public.sqlserver.security)
  • Re: public role question
    ... If 'select user' is returning DBO, it means you are connecting AS DBO, and ... testing the permissions the new user has. ... Are you saying that the permissions to create the stored procedure are ... Dan D. ...
    (microsoft.public.sqlserver.security)
  • Re: How to prevent DELETEs in a table
    ... What you say about dbo is true, but it is even MORE true about someone who ... is in the sysadmin role. ... No permissions are ever checked for someone in the ... the deny is not applied. ...
    (microsoft.public.sqlserver.server)
  • Re: How to prevent DELETEs in a table
    ... It is the dbo database USER, not server-level groups, that determins ... It has implicit permissions that can not be denied. ... SQL Server just skips any permission validation for sysadmins. ...
    (microsoft.public.sqlserver.server)
  • Re: Control over creation of procs & views owned by dbo
    ... To add on to Jasper's response, you could also change object ownership to ... 'dbo' with sp_changeobjectowner. ... security context of the invoking user, not the object owner. ... need permissions on only directly referenced objects. ...
    (microsoft.public.sqlserver.security)