Those numbers are based off of the developers who are tied to a database in
some fashion. The numbers are much higher when you look at all developers on
the teams you may support who do no development against a database.
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf
Of dimensional.dba@xxxxxxxxxxx
Sent: Monday, January 28, 2019 9:23 AM
To: backseatdba@xxxxxxxxx; 'oracle-l-freelist' <oracle-l@xxxxxxxxxxxxx>
Subject: RE: DBA to Developer ratio
As you said it really depends.
In the consulting world for contracts I have seen 4 to 1, when calculating DBA
to Developers.
In the commercial world I have seen upwards of 75 developers to 1 DBA. And a
low of about 6 Developers to 1 DBA.
Really depends on how much help the Developers need or how much control of them
you need.
Can you keep up with the project time lines based on your ratio and their/your
needs.
From: oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx>
<oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx> > On
Behalf Of Jeff Chirco
Sent: Monday, January 28, 2019 9:12 AM
To: oracle-l-freelist <oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx> >
Subject: DBA to Developer ratio
I know this is not an exact science and every company is different and a lot of
factors goes into this. But just curious how many DBA's you have compared to
how many developers? We do mostly custom development of many applications for
the company. We have 20 developers that do .Net, Web, Cobol, VB, and just
starting APEX. They all also do their own PL/SQL, which we review. There is 2
of us as DBA's who also do development. We support 5 Oracle databases and a
bunch of MSQL databases but those are all third party systems.
Is there a common or magic number?
Jeff
