Thanks Sue but I think I'm still stuck. ESRI's GIS (Geographic
Information System) employs another database to store metadata and
geometry information for GIS objects in the database. The
sp_changeobjectowner doesn't know about this other database. Using
the command will corrupt the database. :(
On Wed, 19 May 2004 13:03:44 -0600, "Sue Hoegemeier"
[quoted text, click to view] <Sue_H@nomail.please> wrote:
>Randy,
>You could change the object owners after the fact using:
>sp_changeobjectowner
>
>-Sue
>
>"Randy K" <wawork@hotmail.com> wrote in message
>news:40ab7851.718750@msnews.microsoft.com...
>> 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
>> >
>>
>
>
