An now for the devil's advocate : what about having one application
becoming so successful that somebody decides that it needs its proper
server ? Migration, anybody ? Or if one application is supposed to run
24x7 with most of others doing a 5 days a week 9 to 5 ? Or if one
application is developed with a client tool T1, another one with another
client tool T2, and that a bug in T2 requires an Oracle upgrade
unsupported by T1 ? Database splits may occur.
I don't think that there is a simple answer. Our aim usually is to
minimise future pain by smartly anticipating on weird requirements
coming from elsewhere which you will be unable to fend off. Try to guess
what your database will be in a few months, and choose the organisation
which minimises the number of W/E spent in front of a screen.
--
Regards,
Stephane Faroult
email: sfaroult_at_oriolecorp.com
Oriole Corporation
Voice: +44 (0) 7050-696-269
Fax: +44 (0) 7050-696-449
Performance Tools & Free Scripts
------------------------------------------------------------------
http://www.oriolecorp.com, designed by Oracle DBAs for Oracle DBAs
------------------------------------------------------------------
>
> One of the problems you will encounter with one schema owner is the deletion of data with
> the truncate command. In order to be able to use the truncate command the user has to be
> given the "delete any table " grant. To get around this problem I have build those tables in
> the schema of the user with the need for the grant and then applied the other needed grants
> to the other users. I feel that it is easier to manage the privileges to the tables with one
> owner where applicable and use different roles for different access needs.
> HTH
> ROR ª¿ª
>
> >>> beckerb_at_mfldclin.edu 10/18/00 10:20AM >>>
> Hello,
>
> Is there any accepted best practice regarding schema management?
> We are a small datawarehouse experiencing growing pains;
> currently, we use a different owner account for each application area,
> but applications are frequently crossing schema boundaries and using
> tables from several schemas. The suggestion has been made to use
> a single schema which would own everything, and control privileges
> entirely thru roles. This would simplify development, but I wonder what
> the disadvantages would be (other than the security concern over having
> everything in one schema; is this something to worry about?).
> Using Oracle 8.1.6 on Solaris with Cognos tools.
>
> Thanks to any responders.
Received on Wed Oct 18 2000 - 09:52:40 CDT
