Marc Blum wrote:
> On Fri, 26 Oct 2007 23:11:51 -0700, DA Morgan <damorgan_at_psoug.org> wrote:
>
>> Here I agree and I will go one step further. No developer should ever
>> have access to a production database except as an end-user utilizing the
>> application. I've yet to see a legitimate reason for any developer to
>> have production access privs.
>
> Maybe because there's some urgent issue to be solved, maybe production ist
> coming to a grinding halt and there's a need for someone who knows the
> requirements and the implementation and the technology to get rid of the issue
> NOW! Production DBAs fail in the first and second point.
If they do then at the very least the change control process if not the
entire development process has failed. Surely the scenario above can
only happen where the developers know what they are doing, why they are
doing it and what they are doing it with - but unaccountably fail to
tell anyone any of this? Equally a DBA that lets code to production with
no idea of purpose, scope or impact isn't worth the name. Mind you for
all of the folks that have setups where the developers know the business
and the dbas don't I sure hope the support calls all go to the
developers first - anything else would be a misroute.
--
Niall Litchfield
Oracle DBA
http://www.orawin.info/services
Received on Sat Nov 03 2007 - 16:23:42 CDT
