December 10, 2002 at 10:14 am
Unlike an NTFS file or folder a sql 2k database can apparently have multiple
owers (i.e. dbo's). Should this "feature" be avoided or embraced?
TIA,
Bill
December 10, 2002 at 10:20 am
In production, avoided. Though in my world, with dozens of servers, we have to let some people manage their db while we manage the server.
In dev, I try to avoid it, but it's not always possible. It does make things easier when someone else manages the dbos.
Steve Jones
December 10, 2002 at 10:58 am
Like most open ended questions: It depends.
As noted, farming out responsibility can be a good thing. It offloads the app design tasks to the folks who know the app. Your DBAs can manage the data base and environment.
What we generally do is create 3 IDs for each application: an AppDBA ID, an AppDEV ID and an AppUser ID. The AppDBA can create tables, views, etc. The AppDev can create stored procs and views but not modify tables, indexes, etc (DBA stuff).
The AppUser can only EXECUTE stored procs. It has no access to any other data base objects. This has worked well for 5+ years.
December 10, 2002 at 11:27 am
I agree, only when absolutely needed for a specific reason do. But for the most part try to keep control of the environment and it's quality by only having one or a specific group.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply