I'm not entirely sure what you're looking for here. There are probably as many "types" of "DBA" as there are DBAs in the world. I seriously doubt any two have exactly identical duties, skills, expectations, etc.
The key to being a DBA is flexibility, both in scope and strength of skills, and in focus of duties and projects.
Last week, I spent most of the week administering databases and servers. I wrote up some scripts I've been meaning to do for a long while, since I finally had time for them, and automated some reports to myself from the servers. Database growth charts, smarter index cleanup, a few things like that.
This week, I'm debugging an ETL process that was originally implemented based on flawed understanding of the business rules.
A few months ago, I was cleaning up millions of rows of data that had duplicates, fuzzy matches, etc., and doing complex pattern analysis on things like multinational names and addresses.
Today I had to debug a stored procedure that was failing without raising an error message.
Next month, I'll be upgrading a server to SQL 2008 R2, including upgrading all the SSIS packages on it.
There are plans, early next year, to build a whole new set of on-site database servers, with a serious hardware upgrade at all levels (CPUs, SAN, you name it).
What "type" of DBA does that make me?
My job before this one, the main emphasis was on setting up SSRS and on a DR plan implementation. What type of DBA does those two things?
So, don't worry about the specific titles. They usually don't mean much, in the real world, anyway.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon