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 123»»»

The DBA Dilemma: How Many DBAs Does It Take to Manage an Infrastructure? Expand / Collapse
Author
Message
Posted Monday, October 26, 2009 9:00 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, August 8, 2014 6:02 AM
Points: 32, Visits: 595
Comments posted to this topic are about the item The DBA Dilemma: How Many DBAs Does It Take to Manage an Infrastructure?
Post #809063
Posted Monday, October 26, 2009 11:21 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, May 15, 2014 5:11 PM
Points: 6,067, Visits: 5,283
I think this depends greatly on the infrastructure you have in place. If you don't have a good infrstructure the number of servers that any single DBA can handle is greatly diminished. Just think about patching, how many servers can you patch at once manually? I can think of all kinds of monitoring that you might need.. But just off the of my head..

1. Services running, SQL and Agent.
2. Services active, SQL responds to logins, Agent is running jobs.
3. Errorlog is monitored for issues.

Any other thoughts?

CEWII
Post #809089
Posted Tuesday, October 27, 2009 3:37 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, March 6, 2014 1:05 PM
Points: 1,334, Visits: 3,068
Elliott W (10/26/2009)
I think this depends greatly on the infrastructure you have in place. If you don't have a good infrstructure the number of servers that any single DBA can handle is greatly diminished. Just think about patching, how many servers can you patch at once manually? I can think of all kinds of monitoring that you might need.. But just off the of my head..

1. Services running, SQL and Agent.
2. Services active, SQL responds to logins, Agent is running jobs.
3. Errorlog is monitored for issues.

Any other thoughts?

CEWII


I agree, this does tend to depend in what shape your infrastructure is in to begin with. Automated morning reporting on nightly backup routine status, errorlog checking, failed jobs, blocked or blocking processes, phyical disk alerts, etc. goes along way here to extend this number of servers a DBA can easily handle, at least it does for me anyway. Also, now with the release of SQL 2008 the DBA now has at his disposal two new features known as CMS (Central Management Servers) and PBM (Policy Based Management) that allow the DBA to deal with and maintain multiple db servers as a collective unit or group. Instead of having to deal with each of them individually. But of course, you need to get all of this in place first, and that can take some time to do. Not to mention that you might have to put out some major fires beforehand and get your infrastructure under control even before implementing automation and central management. However, the nice thing about this needed front work though is once you got it setup and organized once, then you are golden. Your daily admiistrator life immediately starts to get better, trust me. Adding servers to this mix after that point is a piece of cake. It is definitely worth the effort IMHO. It just all depends on what shape your production db servers are in and this tends to varies widely from company to company in my past experience. :) I have seen some DBA's that have not got the 10 db servers that they are reponsible for organized and automated, and they end up chasing their tails all day long never really getting much accomplished. Then I have seen other DBA's that got 50+ db servers nice and automated, centralized, and organized and manage them quite well, with plenty of time to spare....and not to mention what your boss will think come evaluation time...


"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ..."
Post #809161
Posted Tuesday, October 27, 2009 5:31 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, September 27, 2012 9:09 PM
Points: 136, Visits: 383
I have a team of 4 DBAs - 2 SQL and 2 Oracle. We manage administer:

270 SQL Servers -dev, test, UAT and production
70 Oracle on Linux servers - dev, test, UAT and production

So, thats 135 servers/SQL DBA and 35/Oracle DBA.

The only we we can achieve this is by working 24x7 and not taking any sick days or vacation .

But, seriously, we achieve this through standardising on builds, monitoring scripts and alerting. Most of our servers are exactly the same in configuration. When we perform tasks we always do it on server groups not individual servers. Strict change management also helps here.

We're helped to a degree by a seperate infrastructure team who builds the servers and a tier 1 support team who respond to alerts. Also, many of our servers are commodity, 'scale-out' servers so even the databases are exactly the same.

Oracle DBAs perform secondary support to SQL and Vice Versa.

Its pretty tough and we could do with a couple more DBAs but the budget aint there. Its the 'new normal' i.e. doing more with less.

In a previous post at a gaming company who solely used SQL Server the ratio was 10:1 - we had 10 DBAs and about 120 servers to manage. In hindsight this was overkill and I only realise now how much you can save by standardisng kit and unifying your processes instead of adding more and more DBAs.






thanks

SQL_EXPAT
Post #809212
Posted Tuesday, October 27, 2009 6:05 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 7:36 PM
Points: 6,593, Visits: 8,874
I assume you're counting a server as an instance of sql server? Thus one physical computer might have several sql servers?

Wayne
Microsoft Certified Master: SQL Server 2008
If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
Links: For better assistance in answering your questions, How to ask a question, Performance Problems, Common date/time routines,
CROSS-TABS and PIVOT tables Part 1 & Part 2, Using APPLY Part 1 & Part 2, Splitting Delimited Strings
Post #809232
Posted Tuesday, October 27, 2009 6:28 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, September 27, 2012 9:09 PM
Points: 136, Visits: 383
In my post I'm referring to physical servers. We only ever install 1 instance of SQL Server per server. Oracle is a little different.

Another thing I must mention is that many of these servers are DR servers. All of our live servers are mirrored between sites either through using Database mirroring, log shipping or running LIVE/LIVE.



thanks

SQL_EXPAT
Post #809243
Posted Tuesday, October 27, 2009 7:16 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Friday, August 6, 2010 2:38 PM
Points: 79, Visits: 488
It is depending on the company.
My past experience was monitoring 40 servers by myself(in Healthcare Industry), now ~ 300 servers all over US (in Financial service) by only 2 DBAs but mainly all maintenance job monitors by myself the other is senior DBA ( mainly in Application).
For monitor ~300 servers, it is very easy by a script and let it pages us when it has the problem.
Big problem always comes from a disk problem, need to change server and pretty much we have all backup files and some database files to recover.
Backup, Update stats,DBCC, shrink the file, restart service etc, all done by jobs by the server itself or from monitoring server.
All can be done by set one computer as monitoring server.
All update can be done automatically by the network process.
IMHO, reply to the question, How many DBAs Does it take to manage infrastructure? It should be 0 (zero) in nearly future.
No need DBA for infrastructure in the future.
(Some Company still needs Database Developer for the future).
It is possible, let Network guy install server and SQL server. Monitoring Server can detect the new server, install all jobs automatically by itself.
Post #809279
Posted Tuesday, October 27, 2009 7:31 AM


SSC-Dedicated

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

Group: Administrators
Last Login: Yesterday @ 4:05 PM
Points: 33,165, Visits: 15,299
We had a similar setup to AJs when I was at JD Edwards. Production instances, almost all 1 instance / physical server, were in the 200-300 range. Two DBAs.

We also helped support some development environments at times as well. We weren't slammed most of the time, but it was constant tinkering, monitoring, making sure that the stuff we'd set up to alert us ahead of time was working. And of course, something is always broken with 100s of instances.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #809295
Posted Tuesday, October 27, 2009 8:13 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 8:50 AM
Points: 2,867, Visits: 718
We only have 8 sql servers and 2 dba's. We would be better off with only 1 dba and 1 database developer. I am a little bored with so little to maintain. I came from a shop with 50 sql servers with 2 dba's and 4 database developers, this was much better. Right now my biggest challenge is to stay busy and keep learning new stuff.
Post #809339
Posted Tuesday, October 27, 2009 9:22 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, May 15, 2014 5:11 PM
Points: 6,067, Visits: 5,283
I read one person suggest having one server monitor them all, which in general is good, BUT, you still need to have something monitor the monitor server, at least a little bit.

I mean if you regularly get notified of things and then all of a sudden don't, you might not notice it for a while, even if the secondary monitoring is just are the services running and responding should be probably good enough..

I keep reading this in the posts..
Bad/poor/no infrastructure and change control = Lots of DBA bad days..

CEWII
Post #809397
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse