From: Walter T Rejuney <BlueSax@Unforgetable.com>
Newsgroups: comp.databases.oracle.misc
Subject: Re: Thanks for nothing!!!
Date: Tue, 10 Oct 2000 15:01:36 -0400
Organization: xyzzy
Lines: 26
Message-ID: <39E36790.81713DB2@Unforgetable.com>
References: <39DDEBCC.A09A6F55@hsv.boeing.com> <8rliiv$vib$1@nnrp1.deja.com> <39E21276.DF1C6424@hsv.boeing.com> <39e34eb3$1@rpc1284.daytonoh.ncr.com>
Reply-To: BlueSax@Unforgetable.com
NNTP-Posting-Host: ga0235kstahl.mmr.avaya.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.73 [en] (Win95; U)
X-Accept-Language: en


Jim Gregory wrote:

> You don't really get it.  We cannot help you without information like what
> are the developers doing?  Do they need to create tables, procedures,
> triggers?  Do they need to access each others objects?  Do they need a
> sub-set of DBA privs?  Does the application code that the users run need to
> create tables, indexes, other objects?  Do they need to run stored
> procedures? Do some users update tables while others only do selects?  Do
> the users log in as themselves and need access to 1 or more schema's data or
> do they log in as the owner of the objects?
>
> The most basic documentation contains information on the privileges, roles,
> grants, and synonyms that make up the ORACLE security sub-system.  Sequence
> values stored in table columns need nothing more than regular access to the
> table/columns.  Sequences themselves need to have grants and synonyms set up
> to be accessible to others - just like any other object in ORACLE.
>
> ORACLE is a very complex animal.  Some questions that may seem simple do not
> have simple or easy answers.
>

Unfortunately way to many people want Oracle to work in the same way as
SqlServer. They get a little bit of experience with that toy database and want
to translate the experience to an enterprise-level database like Oracle and then
become frustrated when the real thing doesn't work in the same way as the toy.


