“A good DBA may relax and put his legs on the table”. These words a senior (in age as well as in experience) DBA used to say while he was trying to teach me the basics of administrating databases. He was trying to say that organizing your work and preparing yourself for future catastrophes is the most important part of the job. Only then you are confident to face the surprises Oracle software and the organisation where you work for comes up with.
But as time passes by I disagree with this attitude. In my opinion a good DBA has always work to do. But it’s not always easy to convince your manager you are busy as hell. What ARE you doing all day long, or moreover, what meaningful pro-active contributions you possibly can do for your company to keep the business online? And how can you make it visible to your manager. I´m convinced that in most organisations the attitude towards DBA´s is quite respectfull, but that was and is not always the case and this writing is for those who continuously struggle with the aspects a DBA is doing or is supposed to do.
In this post I’ll try to summarize the deliverables for a DBA as a kind of checklist. Thought about it what base to choose for this kind of list. Had the choice for methods as ITIL, ASL (Application Services Library) ISM (Integrated Service Management), COBIT ( Control Objectives for Information and related Technology) and more. Decided to keep it simple, using a lot of ITIL (v2, cause I’m lost with v3):