Re: Conceptual Data Model (Federal Enterprise Architecture)

I have been lucky enough to stay in positions where the DBA does have these responsibilities
and most of the developers I have worked with love it when you can show them ways to
use the database and therefore eliminating the amount of work they have to do after the
implementation of the next application.

The technical folks of today just don't put enough credit into doing a job right to begin with. It
is always "just get it done and we will fix it later"

Most real experienced DBA's are data architects, system architects, and application architects
as well as administrators of the database.

Just my .02

Mike

On 7/23/2013 6:08 PM, Mark W. Farnham wrote:
> Well we've run straight into a generational difference between modern
> "operational" DBAs and DBAs of years past when experienced developers were
> chosen to become database administrators and supply the development surgical
> team (see Brooks, Man-month, Mythical) with a data model (be it network,
> Codasyl, IMF, Cobol identifications, PL/I structures, or relational [since
> 1969 in theory, about 1973 in practice with the development of DaTaSyS, W,
> R, and what-have-you and the public release of Oracle in 1977]).
>
> Now I guess we call folks who do that Data Architects (at least until the
> AIA sues someone for misusing the term Architect.)
>
> DBAs also had responsibilities for security and granting access to any
> programs which in turn could access data assets of the corporation.
>
> Finally, DBAs had responsibility for setting up JCL and the like for
> operators to run.
>
> But I'm not out to start a religious war and I realize that the bulk of
> folks with the title DBA manage operational databases these days.
>

--
http://www.freelists.org/webpage/oracle-l