I'm a newbie with Procedure Builder, so if this question seems
ignorant, please bear with me.
I've been creating small SQL+PL/SQL routines for a while and
have gotten stored procedure/function packages working. My progs
are now getting a bit complex for a text editor and trial-and-error
debugging. I've convinced my chief to purchase the Procedure Builder
module licence. There is a Developer 2000 library setup script that
has to run logged in as SYSTEM in order to set up a database on the
server for Object Navigator to store modules in a library on the
server. Right now, it's just me, but there may be more people from
our group in future.
While our group reports to the same director as the DBA, and we're
on good terms with him, and just down the hall from him, I don't
want to have to go running to him every time our group adds or
removes another programmer or decides to make another module visible
to PUBLIC or a restricted group of users. Questions...
- Does this database absolutely have to be set up under SYSTEM?
- If yes to 1), is it possible for the DBA to grant me a restricted
subset of grant/revoke privileges so that I could do the minor
housekeeping without bugging him every time? Implicit in this
question is that those "lesser god" powers shouldn't create a
security risk or allow me access to other groups' libraries if
they also get into Developer 2000 or parts thereof.
--
Walter Dnes <waltdnes_at_interlog.com> procmail spamfilter
http://www.interlog.com/~waltdnes/spamdunk/spamdunk.htm
Why a fiscal conservative opposes Toronto 2008 OWE-lympics
http://www.interlog.com/~waltdnes/owe-lympics/owe-lympics.htm
Received on Fri Apr 30 1999 - 22:58:54 CDT
