RE: Re[2]: What Sort of Privilege?

  • From: "Ron Rogers" <RROGERS@xxxxxxxxxxxxx>
  • To: <oracle-l@xxxxxxxxxxxxx>
  • Date: Tue, 24 Aug 2004 09:47:54 -0400

The many schema method is easy to handle. The schema owner grants
privileges to the dba with admin option
and the dba controls the roles. The schema owner/user can only "see"
the tables that they own or are granted
access to. With many schemas sharing a few "common"  tables from the
majority( size wise) of the database, control and access
is easy. We have 11 in house applications that have thier own schemas
and 1 large warehouse type application on the database.
No problems keeping everyone seperated.
Ron

>>> DGoulet@xxxxxxxx 08/24/2004 9:12:00 AM >>>
Tom,

        Sorry, but you are wrong.  I prefer the many schema method as
well.

Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA

-----Original Message-----
From: Mercadante, Thomas F [mailto:thomas.mercadante@xxxxxxxxxxxxxxxxx]

Sent: Tuesday, August 24, 2004 8:21 AM
To: 'oracle-l@xxxxxxxxxxxxx'
Subject: RE: Re[2]: What Sort of Privilege?


Jo,

Well,  The Oracle Apps applications have many schema's - much like what
=
you
described.
I'm guessing that the majority of home-grown applications have only
one
schema for all of the tables.  I could be wrong.  In my view, it is =
easier
to manage.  Everything is in one place.  It prevents you from creating
=
two
database objects with the same name.  Managing security is easier - =
again,
you can issue all your grants from one schema, rather than needing to
=
keep
re-logging in.

Maybe it's just me!

Tom Mercadante
Oracle Certified Professional


-----Original Message-----
From: jo_holvoet@xxxxxxxx [mailto:jo_holvoet@xxxxxxxx]=20 
Sent: Tuesday, August 24, 2004 8:13 AM
To: oracle-l@xxxxxxxxxxxxx 
Cc: 'oracle-l@xxxxxxxxxxxxx'; oracle-l-bounce@xxxxxxxxxxxxx 
Subject: RE: Re[2]: What Sort of Privilege?


Hi Tom,

we (well, it was in place before I got here, but anyway) basically
have=20
one schema per application. We also have one schema which houses =
"common"=20
data, i.e. data used in many different places/apps; e.g. employees,=20
customers, products, plants, .... So we have many cross-schema FKs to
=
the=20
"common" data but outside that everything is pretty well
partitioned.=20
Maybe that's why I've never really had any problems with it.

Is having what is basically a one-schema database common practice ?

mvg/regards

Jo



----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Other related posts: