Janet,
You have to create roles and put in these roles users/groups who need the
access level that you first defined.
So yes giving everyone dbo access is not really good instead your
application is not critical.

Rgds,
Serge

-----Message d'origine-----
De : Mangual Janet A. (WASD)
[mailto:mssqldba-ezmlmshield-x28579053.[Email address protected]
Envoyé : vendredi 18 février 2005 13:03
À : LazyDBA Discussion
Objet : Too many database owners

To all Guru's out there;

We are working with a consultant who is implemented this application and the
database is on our SQL Server database. He had granted dbo to several
accounts, including his, in addition to the account that owned the schema.
My argument is that this is a security problem since anyone who has the dbo
priv can manipulate any object of the schema, even delete them. I don't see
any advantage on this configuration? I need to know what do you guys think?

Janet Mangual
Database Administrator, MIS Division
Miami-Dade Water & Sewer Department



---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: mssqldba-[Email address protected]

MS Sql Server LazyDBA home page