Re: HELP Design question --- Where should I create Application accounts

Without any additional info I'd have to say create one account and a security (user) table(s).

Managing schemas ends up being too much of a pain unless they all have the same security roles and capabilities. Then it's like having one signon anyway.

Again, without hearing anything about the workflow of this app.. I'd create a central schema for all your application tables (en 'enterprise data store') that grants permissions to user-access schemas that relate to the application itself.

So create a schema called ENT_DB (enterprise database) And one schema called ORD_ENT (order-entry application)

Maybe later you'll add a schema called DEL_REP that the application 'Delivery Reports' uses to gain access. Each 'application' schema contains no tables. only permissions to tables in the ENT_DB schema.

It's probably the easiest scenario to administer, while still providing some flexibility in terms of access security.

Seigmund Akinwande Johnson <asjohns_at_midway.uchicago.edu> wrote in message news:3OjW3.92$j4.2318_at_uchinews...
> I am developing an application, that requires 10 users, should I create
one
> oracle user account for the
> application itself or 10 separate oracle accounts.
>
> Creating one application account, would require me to create a user table
> and the application itself uses
> only one account to login, once logged in I can validate users on my own
> user table
>
> Otherwise I simply create the accounts in Oracle, and leave authentication
> to oracle database
>
> --
> Developer
> BSDIS
> 773-834-2652
>
>
Received on Wed Nov 10 1999 - 14:39:24 CST