Application DBA vs. Operational DBA

[jayjaybigs]

I was wondering if anyone has additional input into the above subject. In my view, the differece is as I listed below. Please feel free to add or correct the list with your input.

Operational DBA:
.convert business units to ERD diagram.
.Documentation of data flow withing business units
.Data security and protection
.formulate and document security and integrity steps.

Application DBA:
.create database objects for application data access
.maintain database objects for seamless data access
.maintain database consumers( users, applications)
.formulate proactive steps to guide against data loss.
.Document database management steps.
.Propose anhancement to esnsure database reliable.

After a while the line between Operational and Application DBA becomes blurry.

I am hereby asking for your input, please feel free to move/add to different categories as you see fit.

thanks.

 

[SantaMufasa]

JayJay,

There are no "industry-standard" lines of demarcation between the responsibilities of Operational versus Application DBAs.

For you to clarify responsibilities within your organisation, you must do the following:

1) Identify the lowest-level executive which is organisationally responsible for the success of both Operational and Application DBAs.

2) Request of that executive to identify the charter/mandate/mission/critical success factors of each job title.

3) Given the results of Item #2, the lines of demarcation may become clear and obvious at that point. If there are remaining issues that are not clear, ask for clarification from that executive or how s/he wants you to identify the boundaries of responsibility and co-operation betweeen those two titles.

As far as the responsibility lists that you presented in your original post are concerned, they are certainly fine provided that they positively correlate with your findings from Items 1-3, above.

Mufasa
(aka Dave of Sandy, Utah, USA)
[

http://www.dasages.com:

Providing low-cost remote Database Admin services]
Click here to join Utah Oracle Users Group on Tek-Tips if you use Oracle in Utah USA.

 

[DBAwhosaysNIE]

I would use a slightly different term for tha "application" DBA: development DBA. when I hear "application DBA" I think someone who administers Oracle Applications (ERP, CRM, etc.) which I (personally) don't consider to be a DBA at all.

in our shop the development DBA works with architecture (his actual dept.)/product development to build the schema(s)/queries to support new applications and the operations DBA (me) installs/patches new servers (we have a bunch), runs/test backups/restores, maintains security, manages load balancing/replication, etc. I am lucky in that he/I are both qualified to do the other's role but we're comfortable in our respective ones.

 

[Advocate]

one abbreviated version, me thinks ...

dev dba may analyse requirements, develop solutions, review/advise/tune other developers' sql or pl/sql etc, and support prod dbas where required ...

prod dbas continually monitor production environemt; check all batch jobs have run, system and users are working ok, look for trouble spots, take control of errors, try and resolve errors and liaise with others (incl dev-dbas) for solutions ...

neither the dev or prod dbas are superior to each other as they may require a different skill set and both teams require some very smart cookies ...

gotta sympathise with the prod dbas working under the bosses microscope and pressure though ...

from a dba-wannabee currently working in a multi-disciplined dev-dba team ...


regards, david - no such thing as problems - only solutions.

 

[carp]

I've been having this argument with our DBAs for several years now. We are running Oracle 11i Apps on a 9i database. They keep wanting to call themselves "Apps DBAs", and I keep telling them there is no such thing! A DBA is a DBA is a DBA. Their primary job is the proper care and feeding of the database. As Advocate points out, their emphasis may differ depending on the database's purpose, but their primary mission is still to keep the database alive and well.
If you look in the Oracle Applications manuals, you will find Oracle appears to support my position - they describe roles for "Database Administrators" and "Applications Administrators". The two are completely different. However, I think the confusion comes from the fact that many (if not most) businesses assign the Applications Administrator role to the DBAs.
Another way to look at this would be to consider - how many databases do NOT support any applications? I would suggest such a database has no purpose; consequently, ALL DBAs would then be defined as Apps DBAs.
My USD.02.