Re: Managing developers recommendations
- From: Richard Ji <richard.c.ji@xxxxxxxxx>
- To: Herring Dave - dherri <Dave.Herring@xxxxxxxxxx>
- Date: Mon, 24 Oct 2005 11:05:55 -0400
Fair enough. But then you got to do:
1. Educate those who have read only access to production on, what's allowed
and more importantly what's NOT allowed to do.
2. If TOAD isn't controllable, find something else that you can.
After all, you ARE the administrator not your management. Because
when shit hits the fan, you are going to get called. So you should show them
that you have authority over it. If my management is trying to overwrite
my authority on DB, then I will let them know all the risks. They probably
and likely don't know the risks when your TOAD user does "select * from
huge_table."
or issue a lock on your transaction table. I know your manager hired you,
but
they hired you to do exactly that, tell them what's good to do and what's
not good
to do.
Richard
On 10/24/05, Herring Dave - dherri <Dave.Herring@xxxxxxxxxx> wrote:
>
> Unfortunately I don't have much choice. If management tells me that
> person A, B, and C need read-only access to production tables to
> periodically review a sample of data for accuracy, I've got to do it. If the
> production team tells me that x number of support folks need read-only
> access to production tables to be able to resolve production issues, I've
> got to do it. In both cases, they use TOAD and I observe the periodic full
> scanning of large tables.
>
> Dave
>
> -------------------------------------
>
> Dave Herring, DBA
>
> Acxiom Corporation
>
> 3333 Finley
>
> Downers Grove, IL 60515
>
> wk: 630.944.4762
>
Other related posts:
