Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Managing developers recommendations

Re: Managing developers recommendations

From: Fred Smith <>
Date: Wed, 12 Oct 2005 17:06:00 -0400
Message-ID: <BAY107-F17E9C91CA85E53711FA1AFFE7B0@phx.gbl>

Unfortunately that is true, I just started here and my first order of business is to attempt to create some order out of this chaos. Currently, all developers log in as the same user (the user who owns all of the tables/objects of the application). My fear is that if all developers use this account with TOAD, they will "accidentally" drop important objects left-and-right.

Ideally I want to hold off on releasing TOAD to developers until I can lock down the development arena by doing as you said ... creating individual developer accounts.

I was just wondering if there is any interim solution such as a trimmed-down TOAD version.

(Unfortunately getting every developer to use an individual deverloper account is not an overnight process around here, there are dozens of cron jobs that run with a hardcoded username/password, etc.) So all of those processes will need to be changed so everyone can't just login and see the individual accounts.

Thanks for all the tips, you are adding to my arsenal of reasons that justify my objective of creating some order around here!!

-Fred S.

>Subject: Re: Managing developers recommendations
>Date: Wed, 12 Oct 2005 16:58:27 -0400 (EDT)
>Toad w/ DBA module or who have access to generic schemas that contain
>important data == bad.
>Regular Toad with individual developer accounts, no insert/update/delete
>access on important tables, roles, role-level security and limits on the
>autoextend feature for specific tablespaces == good practice.
>my one big complaint about toad: by default it comes with "autocommit off"
>... which is fine, but it means every session opened to a schema in the
>database has an implicit "begin transaction" attached to it, so you've
>got lots of uncommitted/open transactions ... which can block processes
>from time to time.
>Sounds like you've got a very unorganized dev environment going on ... your
>problem isn't the use of Toad, its the lack of a properly configured
>workspace for your programmers.
> >
> > 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
> > developers. (I don't trust my developers with creating tablespaces,
> > 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
> >
> >
> > --
> >
> >

Donít just search. Find. Check out the new MSN Search!
Received on Wed Oct 12 2005 - 16:08:12 CDT

Original text of this message