Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


The Ratio


The Ratio

Author
Message
OCTom
OCTom
SSCrazy
SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)

Group: General Forum Members
Points: 2813 Visits: 4152
I have never worked in a shop that had even one DBA. My entire career of 30+ years has been small shops with four developers at most. I am the sole developer and we have two net admins. I am what some have called an accidental DBA. I've been pulled kicking and screaming into the DBA world. :-)

Tom
bartedgerton
bartedgerton
SSC Rookie
SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)

Group: General Forum Members
Points: 40 Visits: 224
We currently have 4 developers and I'm the 1 DBA, which seems like a good ratio. The last company I was at had 8 DBA's and 30-40 developers.

Of course, there is a pretty broad spectrum of what duties are assigned to a DBA. I tend to notice that when you get past a 4:1 ratio, you see the developers writing their own DDL and the DBA tends to be more of a systems administrator. I find that I'm mostly writing SSIS packages and troubleshooting performance issues these days, and I dole out advise on data modeling and the finer points of writing SQL, but very little actual code writing.
yazalpizar_
yazalpizar_
SSC-Enthusiastic
SSC-Enthusiastic (152 reputation)SSC-Enthusiastic (152 reputation)SSC-Enthusiastic (152 reputation)SSC-Enthusiastic (152 reputation)SSC-Enthusiastic (152 reputation)SSC-Enthusiastic (152 reputation)SSC-Enthusiastic (152 reputation)SSC-Enthusiastic (152 reputation)

Group: General Forum Members
Points: 152 Visits: 626
Mostly always being working on small companies with no DBA's and around 5-10 dev. But lat two positions on bigger companies I've seen awfull situation: one DBA for an horde of developers. First place, around 30 developers, 3 or 4 servers and many more instances. Second place, and current work, 4 servers, +20 instances, one DBA and +100 developers. From what I've seen so far, no too much tSQL interest on dev's side and the brand new idea is "MS SQL Server can't scale, let's try NoSQL" Pinch
Anders Pedersen
Anders Pedersen
Ten Centuries
Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)

Group: General Forum Members
Points: 1430 Visits: 876
Anywhere between 1:7 and 1:40. The later was a pure admin type DBA job, the ones with the lower ratio tended to also involve a lot more development and architecture work.

My previous company was most likely the worst. 82 production databases, with dev and test environments for each, 22 developers in house AND supporting an off shore team that could be anything between 5 and 40 people depending on what project was going on. With me as the only DBA (most of the time, for a while had a backup DBA). I was the architect and production DBA, luckily the developers had pretty good T-SQL skills. I quit because of the hours needed to support both on and off shore.
Doctor Who 2
Doctor Who 2
SSC Veteran
SSC Veteran (287 reputation)SSC Veteran (287 reputation)SSC Veteran (287 reputation)SSC Veteran (287 reputation)SSC Veteran (287 reputation)SSC Veteran (287 reputation)SSC Veteran (287 reputation)SSC Veteran (287 reputation)

Group: General Forum Members
Points: 287 Visits: 595
I think the ratio you've seen, of 1 DBA to 10 developers is about right. I'd say it's either that or 1 DBA to 8 developers.

Rod
jeff fisher-291560
jeff fisher-291560
Grasshopper
Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)

Group: General Forum Members
Points: 17 Visits: 364
We have around 10 people in development and one DBA [me] but the real question is how many DBAs take care of how many database/servers? We have around 130 servers with SQL and my last guess was around 700 databases.
pdanes
pdanes
SSC-Addicted
SSC-Addicted (440 reputation)SSC-Addicted (440 reputation)SSC-Addicted (440 reputation)SSC-Addicted (440 reputation)SSC-Addicted (440 reputation)SSC-Addicted (440 reputation)SSC-Addicted (440 reputation)SSC-Addicted (440 reputation)

Group: General Forum Members
Points: 440 Visits: 1350
One DBA (me) supporting one developer (me) servicing around 30 users, running 3 servers. Yes, I'm up to *** in alligators.
cs_troyk
cs_troyk
SSCommitted
SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)

Group: General Forum Members
Points: 1528 Visits: 965
Nice topic, Steve, and I have to say I'm not at all surprised at the numbers people are reporting.

An interesting related question - for those that are "development dba's" or "database developers" (whatever you want to call it - a person that focuses on db design and software development primarily in the db itself, maybe with some DAL and ETL work thrown in), what ratios have you seen? For me, it's usually 1 database specialist per about 10-20 people (although I have been the db specialist on a small team of 5 before).



eric-1064266
eric-1064266
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 13
We're about 15:1 (Dev&QA/Dedicated DBA) 75:5

Breaking it down further (although everyone pitches in):
1 - Architect
2 - Admin/Performance DBAs
2 - BI/ETL Designers

We do train our devs and QA to handle basic admin of their own environments.

I find that the number of concurrent projects is more challenging than simple numbers. 1 DBA can easily handle a large team (25) working a single product. We see challenges with (25) if they're on multiple teams and schedules collide.
Sqlraider
Sqlraider
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2230 Visits: 2234
I was the accidental DBA and the developer at my last job, so 1:1.

At my current job it's 1:7.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search