Re: permissions not working

On Feb 18, 11:52 am, "Dan Guzman" <guzma...@nospam-
online.sbcglobal.net> wrote:
Thanks for the help!  When I do SELECT USER it does give me dbo.  I am
not an expert with networking or with SQL server. Does this mean that
at the windows NT level they have sysadmin rights because I did not
give them these rights on the database?

It is likely that the user in question is a member of the Windows
Administrators group on the SQL Server.  Administrators group members access
the SQL Server via membership of the BUILTIN\Administrators login are
sysadmin role members by default in SQL 2000.  Sysadmin role members are dbo
in all databases and is why Erland suggested you check SELECT USER.

--
Hope this helps.

Dan Guzman
SQL Server MVPhttp://weblogs.sqlteam.com/dang/

"JEM" <J...@xxxxxxxxxxxxxxxxx> wrote in message

news:29eaeae8-dfd3-4ecf-8d8e-3122fb34914b@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Feb 15, 6:21 pm, Erland Sommarskog <esq...@xxxxxxxxxxxxx> wrote:





JEM (J...@xxxxxxxxxxxxxxxxx) writes:
Hi. I have a SQL Server 2000 database,using Windows Authentication,
and have created some new roles and assigned permissions to the
various tables, views and sprocs. However, the permissions are not
working. When I log on as a user in one of the roles, i still have
access to insert, update, delete records in tables that i have
specifically denied permissions on (they should only have select
permissions which they have). I am able to log onto Query Analyzer
and do everything with the table that i should not be able to do. The
user is only a member of public and this role. The objects are all
owned by dbo. Any ideas?

If you say "SELECT USER" what does it say? The name of this user or
does it by chance say "dbo"? In the latter case your login somehow
is a sysadmin member and is of course able to do anything.

--
Erland Sommarskog, SQL Server MVP, esq...@xxxxxxxxxxxxx

Books Online for SQL Server 2005
athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books....
Books Online for SQL Server 2000
athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Thanks for the help!  When I do SELECT USER it does give me dbo.  I am
not an expert with networking or with SQL server. Does this mean that
at the windows NT level they have sysadmin rights because I did not
give them these rights on the database?- Hide quoted text -

- Show quoted text -

That makes sense. I have put in a call to the Network admin who set
up these accounts to discuss. Thanks so much for your help!
.

Relevant Pages

  • Re: Permissions WTF - BUILTIN
    ... We recently migrated from an NT4 domain to a Windows 2003 domain. ... My pc and the SQL server have been moved to the new domain. ... Our nt admins have created a new group for the sql admins/developers on the ... > said i was member of db_owner and not srv role sysadmin...but i am getting ...
    (microsoft.public.sqlserver.security)
  • Re: permissions not working
    ... at the windows NT level they have sysadmin rights because I did not ... It is likely that the user in question is a member of the Windows Administrators group on the SQL Server. ... Administrators group members access the SQL Server via membership of the BUILTIN\Administrators login are sysadmin role members by default in SQL 2000. ...
    (microsoft.public.sqlserver.security)
  • What do you do when no one has sysadmin rights?
    ... We have an installation of SQL Server 2005 that allows windows ... but my understanding was that if you are a ... sysadmin rights to sql server. ...
    (microsoft.public.sqlserver.security)
  • Re: SQL Server 7 Permissions!
    ... Yes it matters if the user is a member of the Windows ... there is a group added to SQL Server called ... So a member of the administrators group ...
    (microsoft.public.sqlserver.security)
  • Re: Security issue when user is member in db_datawriter ?
    ... running Windows "Local Users and Groups" it shows that this user is a member ... Install all current available patches by using windows update ... Install the SQL 2000 Sample Databases ... Close all processes of SQL Server Management Studio ...
    (microsoft.public.sqlserver.security)
Quantcast