Hello,

I'm using TOad and Oracle 11g.

I have a lot of shemas inside an instance... How to organize them?
What I see is a long list of schemas which could be difficult to
manage if number of schemas grows up... For example, I'd like to group
Schema_1, Schema_2 and Schema_3 in something like Group_1, so it could
be seen more organized.

Group_1
Schema_1
Schema_2
Schema_3

Sometimes a java or .net application uses 3 or 4 schemas... these
schemas are in the same instance which has other schemas for other
applications.

Of course, I can use an Excel file to organize schemas, but my
question is if Oracle offer some functionality to do it.

On Fri, 08 Jul 2011 07:31:44 -0700, Big George wrote:

Schemas can belong to various roles. There are pre-defined roles, like
DBA, but you can also create your own like "INTERNAL_USER", "APP_USER",
"DEVELOPER" or alike. You can then group schemas by the used roles.



--
http://mgogala.byethost5.com

On Jul 8, 7:31*am, Big George <jbet... (AT) gmail (DOT) com> wrote:
Schema and user are pretty close to equivalent in Oracle. There
really isn't any built in way to organize them as far as I know.
Depending on what you want to do with this organizing and who is
sharing it, you might just want to make a groups table. Personally,
I'd use the spreadsheet for up to maybe 100, table for more. Much
larger may call for an infrastructure solution.

For the app I work on, it has few schemata but many users and groups
it manages, and it winds up being logically similar to what Mladen
suggested, actual implementation mutating wildly over versions as
various OS's, db engines and web access is supported. I miss the days
when it could simply use unix /etc/groups. It ain't secure unless it
hurts.

jg
--
@home.com is bogus.
"In 2100, if America survives, our descendants will say, “You based
your transport system on WHAT?”" - Dan Seiver, San Diego State
University

Big George:

# I have a lot of shemas inside an instance... How to organize them?

As Joel pointed out there is not a big difference between a user login
and a schema in Oracle. Conceptually to us as a DBA schemas have
objects that belong to them ( tables/views/etc ) while logins are
typically empty but will have roles and/or privileges granted to the
logins.

Toad has a whole bunch of options where you can "filter" out
( ignore ) schemas that are empty ( do not have tables for example ).

A lot of flexibility ... that probably means you do not have to do
anything inside oracle to change the current setup. You probably just
have to figure out what you want and use Toad's filtering etc to show
it the way you want it.