[quote from Books Online]
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.
[/quote]
In you case John should create database objects using statements like
"create table dbo.MyTable ..." or "create procedure dbo.MyProcedure..." etc.
Cristian Lefter, SQL Server MVP
[quoted text, click to view] "Ed" <Ed@discussions.microsoft.com> wrote in message
news:0768C4CA-02A7-4425-BFBE-282C2424D331@microsoft.com...
> hi,
> I assign an employee (John) to be a Database Owner of a database called
> HR.
> Why when he create a database object (table, view, or sp), the owner
> column shows John not DBO
> I thought when System Admin or Database Owner creates a object, the owner
> should be DBO, am I wrong or missing something???
> Thanks
> Ed