Re: Im stuck in a black hole!

In article <3cf132ed_1_at_mk-nntp-1.news.uk.worldonline.com>, you said (and I quote):

Reply to both Paul and Sy:

> > DBAs should most definitely NOT design databases. That has been a common
> > and global problem of RDBMSs since they started. Database Design is a
> > SEPARATE discipline from administration of databases. Unfortunately,
> > there are still too many people in responsible positions in this industry
> > who don't even have a CLUE as to what the difference is.
> >
> Nuno,
>
> I entirely agree with sentences 3 and 4. However, I'm not so sure about
> sentence 1.

I agree. However, I still maintain: the skill set to be a DBA has got nothing to do with database design or application design skill sets.

This does NOT mean that one cannot be both. In fact, most experienced DBAs out there who value their professionalism and want to know as much as possible about databases end up getting involved in the discipline of design. If nothing else so that they can better understand and communicate where the real problems lie. And that is fine.

However, the fact is that almost no DBA training out there provides a base for application and database design. It's a different discipline, that needs different training. The end result is that most DBAs end up learning design as self-study. That can be good and bad. Some never get the basics sorted out. Others go on to become exclusively designers, as that is where they can make the most difference.

Yet a lot of managers expect the DBA to be some sort of all knowing genius who can wave a magical wand, activate the _go_fast parameter and solve all problems in one single pass. The old "silver bullet" syndrome.

Still with us, in many forms. That is of course deranged, as we all know. And even useless: as 9iR2 and later releases of Oracle rollout, the need for performance tuning of the database itself will become less and less relevant. What will still be needed is good db and app design.

> Some DBAs are skilled in both disciplines, and are lucky enough to be
> involved in design decisions from the outset.

Exactly. Some. There are always exceptions. But the vast majority of basic-trained or just-started DBAs have no clue whatsoever about design issues and yet are immediately asked to produce output in this arena. The results can be disastrous.

Not their fault, IMO. But a problem area that must be looked at. The current training of DBAs bears no resemblance whatsoever to the real DBA job out there and how it is evolving. We incur the risk of creating an entire "generation" of absolutely "useless" DBAs.

-- 
Cheers
Nuno Souto
nsouto_at_optushome.com.au.nospam