Actually, a member of the db_ddladmin role can CREATE views and other
objects owned by the dbo user.
But they cannot GRANT themselves rights to SELECT from the view. (That
requires membership in db_owner or db_securityadmin.)
"Kalen Delaney" <replies@public_newsgroups.com> wrote in message news:uHTFp3HqHHA.716@TK2MSFTNGP05.phx.gbl
No, on two counts....
1. DBO is a user name. Other users can be in the db_owner role (or the
ddl_admin role, as mentioned by Russell) and not be the user DBO to create
an object owned by DBO.
2. Any object can be qualified with an owner name. DBO is a default owner
name only. When a user references an unqualified object, SQL Server first
checks to see if the object is owned by the user, then checks to see if the
object is owned by dbo. However, it is recommended that you not rely on
default owners. For several reasons, including performance issues, it is
recommended that you always specify the owner for every object, even if that
owner is the DBO user.
Kalen Delaney, SQL Server MVP
"Michael Tissington" <mtissing
@newsgroups.nospam> wrote in message