Re: How to control developers writting better SQL

In article <8tmv7g$64r$1_at_garnet.tc.umn.edu>,   hause011_at_garnet.tc.umn.edu (Steven Hauser) wrote:
>
> It seems to me that software engineering is more the subject of this
> thread.
>
> What engineering techniques can be used to make good systems?
> Well, read a book or two and check out people who successfully develop
> code.
>
> Some basics that never fail to amaze:
> SEPARATE DEVELOPMENT FROM PRODUCTION SYSTEMS. Yeah, basic, but many
> do not do this at all.
>
> USE CONFIGURATION MANAGEMENT. Source code control and methods
> of packaging and moving code from development to production. Again,
> elemental and many times ignored.
>
> REVIEW AND TEST CODE. Many times never done. Specific techniques
> for databases are easily figured out. Check the optimizer, trace,
> time, lock contention, etc. Review code by others, not one
 developer,
> test by others not the person who wrote the code.
>
> Many people think they are above such mundane techniques and think
> they are too special and talented to be "constrained". They usually
> leave broken systems and cost overruns in their wake.
>
> Chaos can create chaos. I call that chaos theory.
> --
> ---------------------------------------------------------
> Steven Hauser
> email: hause011@tc.umn.edu URL: http://www.sofbot.com/
> ---------------------------------------------------------
>

Chaos DOES create chaos. It is not theory, but natural law.

--
David Fitzjarrell
Oracle Certified DBA


Sent via Deja.com http://www.deja.com/
Before you buy.