Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««1234

The Ratio Expand / Collapse
Author
Message
Posted Monday, October 7, 2013 1:04 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 2:50 AM
Points: 5,200, Visits: 2,826
dogramone (10/6/2013)
The last place I worked for that had in house development and hosting was about 1 to 8. It was a strange mix as one system had two developers and one DBA, the other had two DBAs and about 30 developers. But DBA definition is critical in this one.

We had three people who were called DBAs and had DBA in their title but did no monitoring, no tuning, had no backup responsibility. All they did was some TSQL to collect data or fix TSQL application bugs. It drove me nuts as a former DBA and now BA/PM as their code was all spaghetti, did not know how to tune (just add an index!) and I couldn't even get them to do code formatting for readability. But these guys had been around for 15 or more years so all I could tell management is they are in job protection mode. After them making system changes that made everything crawl after adding several new indices that weren't being used (apart from where they added index hints) and one column that had around 15 indices on it I finally got any *new* code they were deploying over to the DBAs I trusted to tweak, tune and standardise.


They are not DBAs...they are bad developers giving everyone a bad name!!!


Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #1502001
Posted Monday, October 7, 2013 2:18 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 3:45 PM
Points: 2,892, Visits: 1,784
Jeff Moden (10/5/2013)


Heh... you have to trust me on this... You DON'T actually want them to do their own backups.


Backups fine, restores...not so much


LinkedIn Profile
Newbie on www.simple-talk.com
Post #1502023
Posted Monday, October 7, 2013 2:24 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 3:17 AM
Points: 5,233, Visits: 9,467
David.Poole (10/7/2013)
Jeff Moden (10/5/2013)


Heh... you have to trust me on this... You DON'T actually want them to do their own backups.


Backups fine, restores...not so much

I don't mind what they do on their own development servers - happy for them to make their own mistakes!

John
Post #1502026
Posted Monday, October 7, 2013 12:25 PM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, July 25, 2014 2:51 PM
Points: 276, Visits: 1,003
We have one DBA, about 16 developers, and about 10 what I call 'power users'. These 'power' users usually write small queries to get some detail level data from our warehouse. We have our production warehouse, and a 'prod2' copy of that warehouse that we let these 'power' users loose against. in the past they ran against our production warehouse and brought it to it's knees with their code.
Post #1502299
Posted Monday, October 7, 2013 1:43 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, December 17, 2013 12:58 PM
Points: 39, Visits: 30
We have about 5 developers to each DBA, not counting managers. The DBAs do development and production support for SQL Server, Sybase ASE, ORACLE, and DB2.
Post #1502341
Posted Monday, October 7, 2013 4:08 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Yesterday @ 7:56 PM
Points: 36,775, Visits: 31,230
John Mitchell-245523 (10/7/2013)
David.Poole (10/7/2013)
Jeff Moden (10/5/2013)


Heh... you have to trust me on this... You DON'T actually want them to do their own backups.


Backups fine, restores...not so much

I don't mind what they do on their own development servers - happy for them to make their own mistakes!

John


The problem is they don't know how to fix what they blow up and because they tend to hoard backups, they can do a whole lot of damage that I'd rather not have to take the time to fix.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1502403
Posted Tuesday, October 8, 2013 10:18 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 11:06 AM
Points: 2,331, Visits: 2,666
Wow, that is odd. My ratio is 1:10, just like Steve said in the editorial.

- webrunner


-------------------
"Operator! Give me the number for 911!" - Homer Simpson

"A SQL query walks into a bar and sees two tables. He walks up to them and says 'Can I join you?'"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
Post #1502704
Posted Tuesday, October 8, 2013 4:27 PM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Yesterday @ 7:42 PM
Points: 8,567, Visits: 9,071
The ratio is going to depend enormously on what needs doing.

If the shop is doing a little bit of application development but handling hundereds of production servers with big databases and serious availability and disaster recovery requirements, it needs more DBAs than developers.

On the other hand, if it's doing a fair bit of development (which includes schema design) and only has a couple of dozen small to medium production servers to support it ought not to need any DBAs at all, the developers should have automated just about all the things that a production DBA would do.

I guess the ratio should vary from all DBAs and no developers to no DBAs and all developers, depending on what's being done, so the idea that there is some single correct or best ratio is not one I tend to believe in.

Anyway, I have a theory that good database developers can easily pass for DBAs, while good development DBAs can easily pass for developers. And I think the sort of overspecialisatin that produces developers (except very young ones who haven't yet got around to it) who haven't learnt to do database stuff or DBAs (again except very young and inexperienced ones) who can administer and organis recoverability and high availability haven't learnt to develop a schema or high performance sets of queries is a bad thing. So the concept of a ratio of DBAs to developers is a bit meaninglss if you are talking about what I think of as competent not overspecialised people.


Tom
Post #1502866
Posted Sunday, October 13, 2013 12:02 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Yesterday @ 6:51 AM
Points: 27, Visits: 104
4 (Soon to be 5) DBA's, to about 15-17 Developers.

Us DBA's also do all of the SQL Development as well (tables, stored procedures and even OData Web Services)
Post #1504282
« Prev Topic | Next Topic »

Add to briefcase «««1234

Permissions Expand / Collapse