Re: Newbie: I don't understand user permissions for table access
From: Peter the Spate (anonymous_at_discussions.microsoft.com)
Date: 07/28/04
- Next message: Aaron: "Re: Query execution plan different between production/test - same"
- Previous message: Keith Kratochvil: "Re: Newbie: I don't understand user permissions for table access"
- In reply to: Larry Woods: "Re: Newbie: I don't understand user permissions for table access"
- Next in thread: Larry Woods: "Re: Newbie: I don't understand user permissions for table access"
- Reply: Larry Woods: "Re: Newbie: I don't understand user permissions for table access"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 28 Jul 2004 08:08:18 -0700
Hi Larry,
ob_owner means you can do anything to that particular
database. If there are other databases you can attack to
then you may have different access rights.
I would sugest you have a look at
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/architec/8_ar_da_8yur.asp and its sub
groups for a bit of background
Peter
MCDBA
>-----Original Message-----
>My database is remote to my workstation. I am using EM
on the workstation.
>The database has a userid/password (not 'sa') but the
userid has "public"
>and "db_owner" roles. Does the "db_owner" have complete
access to all
>tables/fields WITHOUT specifying anything in the
permissions dialogs?
>
>My "public" role only has "SELECT" and "EXEC" permissions.
>
>Thanks, again.
>
>Larry Woods
>
>And,
>"Keith Kratochvil" <sqlguy.back2u@comcast.net> wrote in
message
>news:%23PTfc5KdEHA.3728@TK2MSFTNGP09.phx.gbl...
>> wrong
>> table permissions are important. They are required in
order to
>> access/update/delete data.
>>
>> HOW are you connecting to SQL Server?
>> NT Authentication?
>> SQL Server Authentication?
>>
>> If SQL Server auth, what account are you using? sa?
If so, that is the
>> "GOD" account. You have full permissions to do
anything and everything.
>>
>> If you are using NT auth, what rights does your NT
account have? Is it
>> assigned server or database roles that allow the
activities that you are
>> performing?
>>
>> Finally, what rights/permissions have been granted to
the PUBLIC role?
>> Often (unfortunately) companies simply grant all rights
to the public
>> role...and then evey account (SQL and NT) inherit the
rights assigned to
>the
>> public role. For obvious reasons this is a bad
security model.
>>
>> SQL Server has a strong security model and it works
well when it is setup
>by
>> someone who knows what they are doing. In the wrong
hands....
>>
>> --
>> Keith
>>
>>
>> "Larry Woods" <larry@NOSPAMlwoods.com> wrote in message
>> news:eM31J1KdEHA.3864@TK2MSFTNGP10.phx.gbl...
>> > I have a SQL Server database that has database
userid/password
>protection.
>> > When I open the database through EM I can
add/delete/modify any table,
>but
>> > when I look at the permissions for any of the tables
there are NO
>options
>> > set for any user of the database! I don't understand
the purpose of the
>> > permissions, I guess, since they don't have to be set
in order to get
>> access
>> > to the tables.
>> >
>> > TIA,
>> >
>> > Larry Woods
>> >
>> >
>>
>
>
>.
>
- Next message: Aaron: "Re: Query execution plan different between production/test - same"
- Previous message: Keith Kratochvil: "Re: Newbie: I don't understand user permissions for table access"
- In reply to: Larry Woods: "Re: Newbie: I don't understand user permissions for table access"
- Next in thread: Larry Woods: "Re: Newbie: I don't understand user permissions for table access"
- Reply: Larry Woods: "Re: Newbie: I don't understand user permissions for table access"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
