Hello,

What are the effects in working with a database owned by a user 'X'? In other
words, what are the differences whether i.e. the owner is 'sa', a user which is
db_owner, or a "normal" user?
[SQL Server 2K]

Thank You

Joachim

Hi
One is that  a "normal user" cannot delete/drop any objects created by
another user.


Show quoteHide quote

Iam not sure what it is that you want to know but when using SQL
Authentication, you can create you own user say userx and make them
owner of the database i.e assign the role db_owner, There is not
different really with using 'sa', but when you are using sa make sure
you have protected your database correctly

You are talking about two different things here.
Making someone the actual owner of a database is NOT the same as putting
them in the db_owner role.

If they are the true owner, their login name will be stored in the
sysdatabases table in the master database, and when they use the database of
which they are the owner, they will have the user name DBO.

A user in the database can be put in the db_owner role, but they still have
their own user name, they are not DBO. Their name is not stored anywhere
outside the database. Within the database they have all the permissions of
the true owner, but they keep their own user name.

Please read about logins, users and database roles in the Books Online.

Show quoteHide quote

SQL 2005 unrestricted log file
SQL Server Enterprise Manager Error
Benefits of 64bit SQL?
SQL Server 2005 and VS2005
FillFactor and Intermeditory Pages
Unable to grant rights to user
Backup
how to simplify what i'm doing (AS the solution?)
Sysindexes table error - cannot repair
SQL server RAID and query parallelism