Re: survey - DBA structure in your company ?
Date: Fri, 3 Apr 2009 10:12:47 +1300
we do #2, in teams of 2-3 DBAs per group of 40-odd databases (600+ oracle databases in total). Each system has a cheatsheet to outline any idiosyncrises, support people etc. It's important to keep this up to date as its used by the oncall DBAs as well. The datatabases are shuffled between teams periodically to give them wider exposure.
MSSQL, DB2, mysql, Informix have their own DBAs.
#1 didn't seem to work too well previously, leads to the silo-mentality ("not my problem" - people doing a half-assed job) and a kind of caste system with the "run" DBAs at the bottom, and the apps/project guys up top.
> We are a reasonably large corporation, with 650 Oracle databases. We are
> having a bit of internal discussion going on concerning different support
> (1) Having separation of duties for DBAs: one DBA area in responsible for
> infrastructure across all databases and another group doing application DBA
> work across multiple application databases, closer to the applications and
> their data or
> (2) Doing DBA work in silos: one DBA would be responsible for a certain set
> of applications and databases end-to-end, responsible for all infrastructure
> and application data work for that set of applications
> We currently have a structure like this:
> We have systems DBAs that are responsible for the database infrastructure -
> installing the server software & patching, tuning at the instance level,
> monitoring db server capacity, backup & recovery, adding sizing datafiles,
> disaster recovery, database creation, user & security administration, 24x7
> level 3 support.
> We have application DBAs that are closer to the application data, and are
> responsible for creating and maintaining the application schema objects
> (tables, indexes, etc), some SQL statement tuning, logical backups (exp/imp)
> of application objects, data loads, 24x7 level 2 support.
> I am curious what other folks are doing.