Re: DBA task for System DBA and Application DBA

We'll, here's a (slightly) different one....

In some shops, the Application DBA works closely with the application developers to make sure that anything database-related, as it pertains to the application, is done the best way possible. In other words, the Application DBA nips application problems in the bud before it is rolled into production. The System DBA, sometimes called a Production DBA is concerned with the production database. The Application DBA and the Production DBA need to work closely together before any application is rolled into production.

Then there is the Applications DBA (not the 's'). This DBA works with the Oracle Applications product.

HTH,
Brian

Burton Peltier wrote:
>
> You will probably get lots of different responses to this question, just 1
> opinion here...
>
> Basically a "System" DBA maintains the databases/instances on the server
> (backups, recovers, create database, tweak init.ora, etc.) and an
> "Application" DBA maintains the Oracle schema (tables,indexes,views,tune
> Sql,etc.).
>
> Note: Another key role is the "System" Admin which is the person responsible
> for the hardware on the server and for the server OS. In some companies this
> is combined (so I hear) with the "System" DBA job. In our company, they are
> separate jobs.
>
> Anyway, the roles/responsibities of the "Application" DBA seem less clear to
> me than the "System" DBA. In some places, the "Application" DBA is
> responsible for everything that happens in a schema (tables, indexes, views,
> etc.) in both Development/Test and Production databases. I think this is too
> inflexible and controlling to the developers.
>
> Having been a developer with this type setup, the DBA could easily become a
> "bottleneck" to getting work done (at least in a Development/Test database).
> Lots of times code changes require data model changes. If you have to wait
> on a DBA for each little change to a data model in a dev/test database , I
> don't see how you get anything done .
>
> However, there are benefits to having this inflexible and controlling
> process for the Production Database. But, it does require more DBAs .
> Another approach would be with a good "change control" process, the DBA
> could be involved in "reviews" before the developer/support staff makes the
> change (depending on changes) in production too. Takes less DBAs and you
> should have a good change control process anyway.
>
> --
> "Rakesh" <dba2050_at_yahoo.com> wrote in message
> news:50b9f0f.0307301738.7b221efa_at_posting.google.com...
> > Hellow
> >
> > Will some one explain me what is difference b/w System DBA and
> > Application DBA,
> > what are the responsibilites of each one
> >
> > I would like to know what is diffrent task these two roles play in a
> > big organization. Assuming the organization can afford both dba as
> > separate person.
> >
> > Thanks

-- 
===================================================================

Brian Peasland
dba_at_remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.


"I can give it to you cheap, quick, and good. Now pick two out of
 the three"