Re: Simple Q re schemas and users

Martin Weichert wrote:

> Holger Peine wrote:
> > I have one user MASTER which creates all the tables (thus all tables
> > end up in the MASTER schema), and many other users (some of them
> > created later at run-time) accessing the tables (sometimes via DML
> > statements, sometimes via stored procedures).
>
> Maybe you should consider the following:
> you may have many real-life users accessing the data, but
> do they really have to be separate Oracle users (with own
> database schemas) as well? Since they don't have any data
> of their own, you probably don't need them. Just create one
> separate Oracle user (or maybe a fixed, small number of them
> if you need distinct roles with different access rights),
> and let different real-life users log on to Oracle as the
> same Oracle user. That way you don't have all the hassle with
> dynamic creation of Oracle users, synonyms, privileges etc.;
> it's enough to do it once in the begining for the fixed number
> of Oracle users.
>
> Hope this helps...
> /Martin

> --

> Martin Weichert, Ph.D. - martin.weichert_at_carmensystems.com
> Carmen Systems AB, Odinsgatan 9, S-411 03 Göteborg, Sweden
> Phone: +46-(0)31-720 81 98 Fax: +46-(0)31-720 81 20

With the added advantages of

• never being able to tell which user accessed the data or made some specific updates, even if you turn on auditing;
• and never being able to disallow access to specific users who may no longer be with the organization.

(I'm mildly surprised at your statements - all the Ph.D.'s I know are quite sensitive to the possibility of unauthorized access and/or unauthorized publication of data.)

Bottom line: what are the cost-benefits to the various scenarios?

--
/Hans
[mailto:`echo $from" | sed "s/yahoo/telusplanet/g"`]