Re: Managing developers recommendations
- From: rjamya <rjamya@xxxxxxxxx>
- To: Dave.Herring@xxxxxxxxxx
- Date: Mon, 24 Oct 2005 10:34:29 -0400
IMHO the problem is not TOAD, but your SETUP. In our environment, only
production, application support have production db access. Under extreme
cases developers do get access, but everything they do is logged and mines
later on to see what they did. QA have their own database, which we do
refresh on demand.
Having said that, we do have the luxury to afford so much hardware to
isolate production from everything else, I understand that this is not true
with everyone. You should look at rolling out read-only version of TOAD for
production if you must.
Raj
On 10/24/05, Herring Dave - dherri <Dave.Herring@xxxxxxxxxx> wrote:
>
> Concerning TOAD on any databases in your envs, do you run into issues
> with people scrolling through data? In TOAD you can enter something
> like 'SELECT * FROM huge_tb', then page down periodically to checkout
> what the data looks like. This isn't an option in more simple tools
> like SQL*Plus Worksheet (all that extra effort of filtering on rownum is
> required).
>
Other related posts:
