Re: Deadly sins againts database performance/scalability

From: Daniel Morgan <damorgan_at_x.washington.edu>
Date: Fri, 28 Nov 2003 10:37:12 -0800
Message-ID: <1070044664.792339@yasure>

Hans Forbrich wrote:

> Galen Boyer wrote:
>

>>On 25 Nov 2003, joel-garry_at_home.com wrote:
>>
>>
>>>Letting developers into the production database.
>>
>>Having DBA's make decisions about an application's database when
>>they haven't been involved in the datamodeling or coding effort.
>>

>
>
> Avoiding DBA (or at least data architect) input during design.
>
> Having developers with no datamodeling experience dictate table and
> column definitions.

A number of you have hit this point from various angles and I would like to try to merge them all and thus throw gasoline on the fire.

There are DBAs that think their job consists of backup-recovery, creating users, and denying access to everything because end-users only create problems. I would cateogize them, for the most part, as DBAs that couldn't write and debug a stored procedure if you threatened them with a sharp object.
There are DBAs that are also competent developers having come up through the ranks and are just sick and tired of developers that throw junk over the cubicle wall, don't run explain plan, don't use bind variables, and haven't a clue of the implications of what they write, and whine like babies when the phrase "code review" is mentioned.
There are developers that are competent and can't understand why DBAs stand in their way trying to get the job done.
There are mnagers that don't have the skill set required to define projects, hire good people, fire bad people, and train those that need more skill to do their job properly.

Tackle number 4 and the other three resolve themselves quickly.

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)

Received on Fri Nov 28 2003 - 12:37:12 CST