Re: dbo issues

From: Russell Fields (rlfields_at_sprynet.com)
Date: 08/29/03 

Date: Fri, 29 Aug 2003 08:55:28 -0400

Paul,

I assume that the database owner (in database properties) is 'sa'. At least
that is what most people do. The database owner account is what maps to the
dbo user, thus automatically creating 'dbo' owned objects. If it was some
other name, like 'penzina', then that name would map to the dbo user

When you say that you set up ClientsMaxcor as dbo, I assume you to actually
mean that they are in the db_owner role. This gives them dbo equivalent
power, but it does not change what user they are. Therefore, they are still
themselves and will create 'mylogin' owned objects.

That is why the guidance since 7.0 was to include the object owner
(sometimes called schema) name in all create and manipulation statements.
So, I believe that you will need to train your users to be explicit.

Russell Fields

"Paul Fell" <penzina@iinet.net.au> wrote in message
news:bea9531b.0308281840.14abaf17@posting.google.com...
> SQL Server 2000
> Win 2000 Server
>
> Our security in SQL Server is governed by User Groups in Wind2K. For
> example we have a user group called ClientsMaxcor with several of our
> users included in this Windows Group Account. This account uses
> Windows authentication to log on to the SQL Server and the database in
> which they have responsibility. We have setup dbo (and public) for
> this account for this database.
>
> The problem is that when the users create an object it gets prefixed
> with their group account name login instead of dbo. How can I set this
> account so that dbo is always used as owner of the object(s). The
> Group account as not been given any server based roles.
>
> Any help much appreciated.
>
> Paul

Relevant Pages

  • Re: Will anyone know this?
    ... You can determine if your login is the database owner with sp_helpdb. ... The only required user in a SQL Server database is dbo and this special ...
    (microsoft.public.sqlserver.security)
  • Re: Developer design Best Practices
    ... > test - they develop them and then I move them, and the owner is dbo. ... > There is NO DBO User in our dev database!! ... just means it is owned by the database owner, ... to have a busy dba monitoring development servers. ...
    (microsoft.public.sqlserver.server)
  • Re: Groups for dbo
    ... Thanks for the instructions on changing the database owner...I suspect ... While dbo is SUPPOSED to be a special user that's not used for routine ... It's probably safer to change the database owner in any event, ... >> I'm still fairly new to SQL Server, and I'm trying to figure something ...
    (microsoft.public.sqlserver.security)
  • Re: ADP/SQL Server 2000 Security Problem
    ... > I originally added the database by detaching it from MSDE 2000 and then ... > I'll also test using a SQL Server account and see what happens. ... >> The owner of the dbo account shouldn't have any effect. ... there are no SQL Server user accounts. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Changing DBO
    ... You need to first change the ownership of the existing objects to 'dbo' ... You can then remove the existing database user ... > I have assigned an SQL account as DBO of a database. ...
    (microsoft.public.sqlserver.security)