Re: Why an organization would need an enterprise DB team

Hi!
"...often taught that it is not necessary" - ahh... that's one of the
reasons why one oftens sees bad performance
when going from development to release...

The good thing of seperating the 2 groups can be, that they can focus on
their skills and ensuring
that install guidelines will be followed.
And yes it's an really good idea to have an DBA in the development team,
but there must me information exchange between the 2 dba-groups (rotating
sounds as good idea).
And you have to ensure that the admin-dba have time for application-dba!
/Bjorn D. Jensen


2007/3/19, Jared Still <jkstill@xxxxxxxxx>:

On 3/19/07, Jared Still <jkstill@xxxxxxxxx> wrote:
>
>
>  "Why is data modeling needed?  The main reason is that systems
> developers are so bad at building files and databases".  George Tilmann - A
> Practical Guide to Logical Data Modeling - McGraw Hill 1993
>
> That hasn't changed much in 14 years.
>
> Much of this ignorance of how an efficient (as in scalable) database
> should work is due to the Microsoft 'black box' programming methods.
> Developers don't know many of the building blocks they use really work,  and
> are not encourage to find out how things work.
>
> You don't need to know all the internals, but you do need some idea of
> how things work to use them efficiently.
>



Just to be clear on this, I think it would be great if all developers had
an interest in how the database work, and the hows and whys of database
design.

The problem just seems to be that they are often taught that it is not
necessary.

--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist


Other related posts: