My take on what a DBA should know.
First off the DBA should be involved from conception. Working with the
Developers and
Designers to insure the logical model has met the design requiremnts.
Building the
referential integrity constraints creating the storage requirements for
tables and indexes
is only the part of implementing the physical model. Often I have to rewrite
code and
denormalize the design because of the bottlenecks that were built into the
application.
What I see alot of coming from being a developer and a designer is a lack of
understanding
the application goals and the poor PL-SQL/SQL that is often written.
Ultimately the DBA is
responsible therefore should be involved to verify that the logical model
can be transformed
into a viable physical model that can provide good performance and is
sustainable over time.
Lots of Developers and Designers (not all) have no clue as to the I/O
requirements and often
implement the logical model and suffer from the lack of understanding and
I/O contention.
I have worked in large and small shops over the years and the projects that
succeed are
those where all the communications lines are open with Developers, Designers
and DBA's.
Those larger companies sometimes have to rework ERD's more often because the
lack of
communication between all the groups and the scope creep that follows.
-----Original Message-----
From: Bui David
[mailto:oracledba-ezmlmshield-x17372599.[Email address protected]
Sent: Wednesday, June 02, 2004 7:52 AM
To: LazyDBA.com Discussion
Subject: RE: [Fwd: DBA as developer/designer too]
a DBA should know to do that, though the dba world is divided into
production DBA and application DBA in a large corporation! Those jobs
should be handled and assited by application DBAs.
-----Original Message-----
From: Mike Brenner
[mailto:oracledba-ezmlmshield-x10788087.[Email address protected]
Sent: Wednesday, June 02, 2004 8:43 AM
To: LazyDBA.com Discussion
Subject: [Fwd: DBA as developer/designer too]
Edwin Uy wrote:
> Just want your 2 cents thoughts on this pls if u don't mind . are DBAs
> nowadays involved with designing the tables from scratch, from
> normalizing/denormalizing, determining what should my primary keys be,
> what tables should be created and named etc. . thought the
> developer/designer should be the one involved with that while DBAs
> advised on indexes for performance purposes and users/permissions for
> security purposes .
Mike Brenner wrote:
In with large overhead budgets, there is money to have
a large number of optional separation of concerns, such
as separating DBAs from developers. This would be
wasteful on a developmental system. It only makes
sense when there is a separate production system,
in which case, you would probably assign your best
developer to be the DBA. Only when the DBA tasks
(particularly backing up the data) become so large
that they take up more than 25 percent of that
developer's time should you consider hiring a
separate DBA.
--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: send a blank email to oracledba-[Email address protected]
By using this list you agree to these
terms:http://www.lazydba.com/legal.html
--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: send a blank email to oracledba-[Email address protected]
By using this list you agree to these
terms:http://www.lazydba.com/legal.html
Oracle LazyDBA home page