Re: Should developers have DBA role?

From: Ryan Gaffuri <rgaffuri_at_cox.net>
Date: 14 Jul 2003 10:49:47 -0700
Message-ID: <1efdad5b.0307140504.4da88c79_at_posting.google.com>


spam1.minus1_at_comjet.com (larry) wrote in message news:<6669c584.0307081318.256a9aee_at_posting.google.com>...
> Hi. Our company has about 20 application developers/architects and one
> certified dba. Our developers both design the databases and build the
> applications. We're confused about what permissions a developer is
> supposed to have. On the one hand, we obviously don't want developers
> to have privileges like shutting down the db. On the other hand, some
> of the Oracle tools, like Change Management Pack, are things that our
> developers need to run. Our developers need to be able to compare and
> synchronize schemas on a routine basis. Yet according to the oracle
> documentation, Change Management Pack requires dba privilege. At the
> same time, the oracle docs discuss how the tool can be used by
> developers. So my question is: Does a developer typically have dba
> access? If not, then what permissions is a developer supposed to have?
> Is there any guidance, from oracle or elsewhere, on this issue? Any
> help appreciated.
>
> Larry

my personal opinion is that it depends on the skill level and interest in learning of your developers. Alot of very good developers have a sound and firm understand of database administration. Having them work closely with DBAs and giving them more access is the way to go.

Also, developers that are willing to learn and improve their DBA skills should be given higher access. Those that are not interested in learning should be given less access. Its really not all that black and white. I think you and your DBA should decide which developers can be trusted with access and which cannot.

I dont like shops that are strict enforcers of a seperation between DBAs and developers since alot of tasks over lap. A good DBA should be able to write PL/SQL and do development. A good developer should have a firm understand of architecture and tuning. It depends on the quality of your developers and more importantly their willingness to learn.

Its also in large part dependent on how good of a communicator your DBA is. Is he willing to help them learn? Its alot more work at first, but Ive found that a DBA who is willing to impart alot of his knowledge on people willing to learn is a DBA who ends up having an easier job down the road.

Now by 'developer' what kind of developer are there? ARe they 'oracle developers'? Or are they software engineers? Received on Mon Jul 14 2003 - 19:49:47 CEST

Original text of this message