Who owns the tables in development environment? (upsizing from Access)
From: Randy K (wawork_at_hotmail.com)
Date: 05/18/04
- Next message: Sue Hoegemeier: "Re: Who owns the tables in development environment? (upsizing from Access)"
- Previous message: Phil K: "Re: Recommended client for showing various db sources?"
- Next in thread: Sue Hoegemeier: "Re: Who owns the tables in development environment? (upsizing from Access)"
- Reply: Sue Hoegemeier: "Re: Who owns the tables in development environment? (upsizing from Access)"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 18 May 2004 21:40:14 GMT
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
- Next message: Sue Hoegemeier: "Re: Who owns the tables in development environment? (upsizing from Access)"
- Previous message: Phil K: "Re: Recommended client for showing various db sources?"
- Next in thread: Sue Hoegemeier: "Re: Who owns the tables in development environment? (upsizing from Access)"
- Reply: Sue Hoegemeier: "Re: Who owns the tables in development environment? (upsizing from Access)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|