How to be a good DBA

Fri Sep 2, 2005 by byrmol

Love: A good DBA loves his data and DBMS. And like any good relationship, they communicate with each other

SQL Server: “What a day! “

DBA: “What happened? “

SQL Server: “Some guy does a batch load and before I have time to update the stats, someone else decides to run the end of month report. It hurt. Can you run a "defrag” on me please?”

DBA: “Of course I can. Do you have the credentials of the user who ran the end of month report?

SQL Server: “Yeah, it’s in the trace table in the admin database.

DBA: “Don’t worry. It won’t happen again” [Picks up blunted butcher’ knife.......]

2. Hair: A good DBA has hair on his face. Beards are preferred, but goatees, moustaches etc will do just fine. Hair serves 2 purposes

1. Every visible grey hair represents just how much you care about your data (See Point 1)

2. Something to fondle when contemplating the higher normal forms.

For the discerning lady DBA, glasses and jewelry make excellent substitutes.

3. Attitude: A good DBA has attitude.

“The sun DOES shine out of my arse, so step back and put some sunscreen on!”

4. Theory: A good DBA has a strong understanding of what a data model is and can describe the principles behind both the relational and hierarchy model.

5. Addictions: A good DBA has chemical addictions. Depending on your culture, select what is right for you. Any (or all) of the following are popular:

Caffeine, nicotine, alcohol, marijuana.

Stay away from the tranquilizer/anesthetics class of chemicals. Any business related meeting is usually an excellent and cheap substitute.

6. History: A good DBA knows the history of the profession and the people who shaped it.

7. Skeptical: A good DBA is extremely skeptical. Having a firm belief in the “"Not Invented Here" ethos (unless the originator has impeccable credentials) is a good sign.

Legacy Comments


robvolk 2005-09-02	re: How to be a good DBA You've got the love, but you forgot the hate: 1a. Hate: A good DBA hates developers, and XML, and management, ESPECIALLY any combination thereof, and most especially one who encompasses all three in one package. Such things are akin to black holes swallowing an entire galaxy, and should be avoided or killed at all costs.

Adam Machanic 2005-09-03	re: How to be a good DBA LOL! Very nice.

Jeff 2005-09-07	re: How to be a good DBA very nice David ! I think I didn't get a job once because I had forgotten to grow a goatee first!!! Stupid, stupid ....

Yak 2005-11-05	re: How to be a good DBA A good DBA can rest his Nutz On Your Chin. If you get in his way, look out, cause a good DBA is not afraid of whipping out his nutz and resting them on your chin.

Nicole 2007-09-08	re: How to be a good DBA LOL

a developer 2008-02-03	re: How to be a good DBA A good dba is a dick. they always get in the way of progress and slow projects down.

John 2009-05-05	re: How to be a good DBA A good DBA simply furthers their manager's agenda which is simply to obfuscate all processes, avoid responsibility with respect to the actual data, turn on remedial monitoring and ignore all requests that go beyond a frickin' ping count, close tickets without reading them, execute deployment scripts with no knowledge of their contents, complain if they have to do anything more than F5 a script, rave that a table needs an index even if it's never selected from, then finally, in a total blowhard way, limit anyone else from being able to do their job since they won't do it. I've worked in half a dozen corporate environments and the DBAs are without question the biggest bunch of frickin' lazy ass bastards I've ever met.

another developer 2009-09-28	re: How to be a good DBA I have to agree with John. DBA's are without a doubt the laziest, most reptilian tossers on the planet. Simply asking them to run a script will have them slithering for cover (their beady little Machiavellian eyes glinting with indignation) behind a wall of Very Important Things To Do That Don't Include Work - Yours In Particular.