Posted by Uri Dimant on 11/21/06 06:40

Peter
BOL says
Database Owner (dbo)
The dbo is a user that has implied permissions to perform all activities in
the database. Any member of the sysadmin fixed server role who uses a
database is mapped to the special user inside each database called dbo.
Also, any object created by any member of the sysadmin fixed server role
belongs to dbo automatically.

For example, if user Andrew is a member of the sysadmin fixed server role
and creates a table T1, T1 belongs to dbo and is qualified as dbo.T1, not as
Andrew.T1. Conversely, if Andrew is not a member of the sysadmin fixed
server role but is a member only of the db_owner fixed database role and
creates a table T1, T1 belongs to Andrew and is qualified as Andrew.T1. The
table belongs to Andrew because he did not qualify the table as dbo.T1.

The dbo user cannot be deleted and is always present in every database.

Only objects created by members of the sysadmin fixed server role (or by the
dbo user) belong to dbo. Objects created by any other user who is not also a
member of the sysadmin fixed server role (including members of the db_owner
fixed database role):

a.. Belong to the user creating the object, not dbo.


b.. Are qualified with the name of the user who created the object.




"Peter Nurse" <PtrNrs@yahoo.com.au> wrote in message
news:1164090859.549657.261440@m73g2000cwd.googlegroups.com...
> Uri Dimant wrote:
>> Hi
>> Grant EXECUTE permissions on stored procedure to the specific user
>
> Thanks Uri,
>
> Yes, all users already have EXECUTE permission - that's not the
> problem. Remember that in the original post, I said . . .
>
> In the above example, if the SPs are owned by dbo (as above),
> CREATE
> TABLE & DROP TABLE use MyUser.tblTest while INSERT & SELECT use
> dbo.tblTest.
>
> . . . that refers to the behaviour when executed by a non-dbo (shall we
> call them underprivileged?) user.
>

[Back to original message]