RE: survey - DBA structure in your company ?

From: Mark W. Farnham <>
Date: Thu, 2 Apr 2009 14:28:16 -0400
Message-ID: <>

I believe the best model is to have the Head DBA of the company be the President and CEO, cross train on everything, and have frequent time set aside by the CEO to discuss strategic information management priorities with the entire DBA team. Paired with the Head Analyst of required company application functionality being the Executive Vice President and co-owner, this turns out to align company investments and priorities in information technology with the best possible compromise of short and long term goals.


Mark W. Farnham
Rightsizing, Inc.

-----Original Message-----
From: [] On Behalf Of dave
Sent: Thursday, April 02, 2009 2:12 PM
Subject: Re: survey - DBA structure in your company ?

I would advise against number two. Unless you have at least 2 DBA's per environment end-to-end. The problem is coverage for sick days, vacations, training, etc.

Are DBA's allowed to move between groups? ie, in your current environment, are DBA's allowed to switch from infrastructure to application?

Personally I like to support an environment end to end. Even if you break them apart like the options you propose there may be some overlap.

The best DBA group I was a part of was structured in an end-to-end fashion but once a year we had to juggle the environments. ie, there were around 10 DBA's supporting multiple environments each. At the end of the year you could elect to keep a couple of the environments but the rest went into a pool. Then we went around the room and each DBA picked a new environment from the pool that they would like to support. This solved the coverage issue and seemed to keep everyone happy.

On Thu, Apr 2, 2009 at 1:51 PM, <> wrote:
> We are a reasonably large corporation, with 650 Oracle databases.  We are
> having a bit of internal discussion going on concerning different support
> models:
> (1) Having separation of duties for DBAs: one DBA area in responsible for
> infrastructure across all databases and another group doing application
> 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
> of applications and databases end-to-end, responsible for all
> 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
> of application objects, data loads, 24x7 level 2 support.
> I am curious what other folks are doing.


Received on Thu Apr 02 2009 - 13:28:16 CDT

Original text of this message