Re: The Steps Taken to be a DBA

> > "Niall Litchfield"
> > > My guess is that the most common paths are either
> > >
> > > development -> (optionally) analyst ->DBA
> >
> > I assume development is the same as a developer.
> >
> > What are the roles of a developer and analyst? they seem to overlap.
>
> They do indeed overlap. In fact all 3 roles overlap. What I had in mind
was
> a loose definition something along these lines
>
> Developer -> Code writer. Responsible for application code.
> Analyst -> Design role transforms user requirements into a functional
design
> (that the developer codes to).
> DBA -> Responsible for maintaining, tuning and securing the
> database/application.

What do you mean by application code? can you give me examples?

> Of course ideally the DBA is heavily involved at the design stage (see
> Howards discourse on the 9i Performance Tuning course for the reasons) and
> in the maintaining and writing of code. Similarly the Analyst may well
> review the design based on actual usage patterns for later development
> phases etc etc.
>
> What actually happens is often." We've bought this package, it runs on
> oracle, the supplier has customised it beyond belief and the performance
> isn't what we were promised. Please tune the database so it works properly
> because we're doing a demo of the system for the Board this afternoon. The
> documentation should be lying around here somewhere. "
Received on Tue Jul 09 2002 - 06:00:29 CDT