RE: how to prevent DBA burnout?

From: Rich Jesse <>
Date: Mon, 30 Mar 2009 10:45:14 -0500 (CDT)
Message-ID: <>

Adding a DBA is not always the answer. Some of us wierdos thrive on being a single point of success, given the proper environment of course:,7

(silly RFC 1738 allowing commas in URLs)

The environment is key! But when the workload elevates beyond the single (super)human DBA and another is needed, careful consideration of the distribution of the new responsibilities must be done. And all the other good stuff, too, when hiring a new soon-to-be-trusted DBA...

My $.02,

> Amen! That's the reason I quit my last job. I was the one-man-dba-team.
> The thing that REALLY killed me is that they had an open position for a SR
> DBA and that position was open for more than a 1.5 YEARS! yeah. just let
> the JR DBA do all the work. He's running things alright. no need to waste
> extra payroll!
> Jeremy
> P Consider the environment. Please don't print this e-mail unless you really
> need to.
> From: []
> On Behalf Of Andrew Kerber
> Sent: Monday, March 30, 2009 10:37 AM
> To:
> Cc:; Oracle L
> Subject: Re: how to prevent DBA burnout?
> have at least two dba's, if not, reasonable up-time expectations. Nothing
> burns out a dba quicker than being on call 24x7, with no one else to take
> the load.
> On Mon, Mar 30, 2009 at 9:24 AM, Robyn
> <<>> wrote:
> Opportunities to learn ... classes, conferences and the chance to share
> ideas with others dealing with similar problems and environments.
> Conferences and symposiums are beneficial on multiple levels - cutting
> training budgets is penny wise and pound foolish.
> Burnout and boredom go hand in hand. Doing the same thing the same way over
> and over again burns people out, as does dealing with the same problems day
> after day.

Received on Mon Mar 30 2009 - 10:45:14 CDT

Original text of this message