RE: Managing developers recommendations
- From: "Justin Cave (DDBC)" <jcave@xxxxxxxxxxx>
- To: <fred_fred_1@xxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 12 Oct 2005 14:38:17 -0600
I certainly wouldn't want to prevent developers from using a GUI if that
would make them more productive developers.
Is there a reason that you can't grant them permission to do only what
you want them to do in the database? TOAD (or any other tool) will be
constrained by the permissions granted to the Oracle user that is
connecting. If developer accounts have permission to create a
tablespace, simply revoke those privileges.
You might consider writing some DDL triggers that save off source code
whenever it is updated if you are concerned about accidental deletes.
It should be relatively easy if you've saved off the code to restore a
dropped procedure. If you happen to have an external source control
system available, you can integrate your source tracking triggers with
that system if you're feeling ambitious.
Justin Cave <jcave@xxxxxxxxxxx>
Distributed Database Consulting, Inc.
http://www.ddbcinc.com
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Fred Smith
Sent: Wednesday, October 12, 2005 4:30 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Managing developers recommendations
Hi all,
My developers (who currently just use SQL Plus) now are wanting to use
Quest TOAD. From what I've used it in the past, it is far too powerful
for
developers. (I don't trust my developers with creating tablespaces,
etc.).
Plus, I've found that TOAD is far too easy to delete objects, etc.
Any recommendations, etc would greatly be appreciated!
-Fred S.
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's
FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
