Re: Who owns the tables in development environment? (upsizing from Access)

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Randy K (wawork_at_hotmail.com)
Date: 05/19/04 

Date: Wed, 19 May 2004 15:11:09 GMT

Thanks Sue I didn't know that about aliasing. I don't see a way to
qualify the owner as dbo when doing Access upsizing. Any ideas?

Also, another tool we use, ESRI's ArcGIS software, doesn't allow us to
to qualify owner when creating tables etc.

Randy

On Tue, 18 May 2004 20:52:33 -0600, Sue Hoegemeier
<Sue_H@nomail.please> wrote:

>Not sure what the issues are you hit with aliasing but you
>wouldn't want to go that route anyway - it's provided for
>backwards compatibility only. A user needs to be a member of
>db_owner or db_ddladmin roles (or sysadmin) to create a
>table owned by dbo. Members of db_owner and db_ddladmin need
>to qualify the owner as dbo.object when they create the
>objects to be owned by dbo.
>
>-Sue
>
>On Tue, 18 May 2004 21:40:14 GMT, wawork@hotmail.com (Randy
>K) wrote:
>
>>I've got two developers who will be upsizing an Access database but
>>also making modifications to the resulting tables in SQL Server 2000.
>>This will be our first in house application with an Access frontend.
>>
>>(A little history.) Usually we alias our developers as DBO in the
>>database using sp_addalias. Aliasing the login of the developer as
>>DBO started in our Sybase shop. Being new to SQL Server we just
>>decided to do the same thing. Unfortunately, a login can not be a
>>user in any database that they are aliased as DBO. Therefore, my
>>developers can't do a ODBC connection to SQL 2000. I determined this
>>when trying to set up the ODBC connections in Windows 2000.
>>
>>We don't want database tables and other objects owned by individual
>>logins since people change jobs and eventually leave. How do others
>>handle things.
>>
>>Thank You!
>>Randy K
>>wawork@hotmail.com
>

Relevant Pages

  • Re: object reference in stoed proc
    ... If you don't qualify the object sql server will first look for the object ... as such it will eventually try dbo. ... implications by not qualifying the objects with the owner. ... all object refences dbo by default anyway within a stored procedure? ...
    (microsoft.public.sqlserver.security)
  • Re: ADP: Cant use stored procedure on remote SQL server
    ... Not only I use dbo everywhere but I ... If you don't mention the owner when creating a new stored procedure, view, ... BTW in the database window, all the stored procedures are followed by ... Check also the owner of the SPInc stored procedure. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: rda push when owner is not dbo.
    ... If I launch the sql query analyzewr and try to run the ... I'm pretty configdent that the owner name not being qualified is the ... > I pull the table with rda to a local table named task. ... > I also created a test table in the same database with owner dbo and I ...
    (microsoft.public.sqlserver.ce)
  • Re: Question about dropping owners permissions...
    ... When a member of the db_owner role creates an object, ... dbo, must the owner must be specified: ... >>> create databases themselves. ... Can anyone help me reach my end goal: Allowing developers to ...
    (microsoft.public.sqlserver.security)
  • Re: not creating tables as dbo anymore ?
    ... Database Owner (dbo) ... existing user ID in the database specified by database_name. ... with the login of the current connection. ...
    (microsoft.public.sqlserver.security)