| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> Re: Multiple DBs - Balancing Act
Hi!
I would put it that way:
1) you got a bunch of databases 2) these databases need work done on them 3) therefore you got a bunch of DBAs
And the dimension ranges are:
Now you just have to match your DBAs with tasks on specific databases. There is no golden rule of how many databases should there be per DBA, it depends and it constantly changes.
I would first concentrate on most important databases:
* deploying/migrating/upgrading should be done by best end of DBAs because
there require careful planning and there are lots of errors you can make
* troubleshooting can be initially done by average DBA, *if* allowed by time
constraints and importantness of database. The tasks can always escalate, if
can't be handled by regular DBA.
* designing should be done by best end of DBAs again, because bad design
brings bad consequences.
* monitoring (and "daily tasks") can be done by junior DBA or even regular
operator if procedures are defined properly.
A lot depends on number of DBAs, though. If you got only 4 DBAs, then just put one as Senior DBA who will appoint tasks, in case of coordination problems, otherwise a small number of intelligent people *should* be able to communicate and deal with problems on their own.
But with bigger number of DBAs, my personal preference would be to split
support and "development" DBAs. Then assign best support people to most
critical databases, based on work needed to be done on database, not number
of DBs or anything like that. The work amount can only be estimated, thus we
never should plan 100% of DBA time to maintenance. All kinds of crisis can
happen, also more work needs to be done when doing migrations etc.. Also,
every skill needed in house, has to be backed up, especially with critical
databases.
Development and production DBAs constantly have meetings to exchange ideas
etc.. Better if they're in same room or at least close to each other.
These are my preferences, others probably have their own opinions...
Tanel.
> This question is for folks who are part of a team that manages
> multiple databases and multiple platforms.
>
> How do you balance the load among your team? We're struggling
> with this concept right now as we're about to add another DBA to
> the group. We've considered such things as quantity (how many DBs
> does each DBA handle), importance (to the company - each DBA has
> 'n' databases, load (this DB is used 'n' times as much as another
> one, experience (of the DBA...do we put a UNIX-familiar person in
> charge of DBs on Windows?) and on and on. But then we stumble on
> quantifying the terms - importance, load, etc. And we have had
> some DBs that we considered 'small' become a major PITA when we
> weren't looking! We just signed a deal making Oracle our DB of
> choice for the next several years, so we could see an explosion
> of stuff.
>
> So I'm asking...how do you do it?
>
> Thanks,
> Mike
>
> ---
>
-- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Tanel Poder INET: tanel.poder.003_at_mail.ee Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).Received on Mon Aug 11 2003 - 18:34:24 CDT
 |
 |