Re: Seeking Database Design Guide

Dave,

In a message dated 97-07-30 17:12:36 EDT, you write:

(LOVE your hamburgers, BTW)

> Sorry for no reference to educational tools.  I'll offer some tips, (this
  
>  should get a flurry of differing opinions!)
>  
>  Get SQL.  If you can't convince mgmt, then learn about Query Management   
>  Facility to do much of the same except imbedded SQL.

I thought that SQL now came w/the system, is this not the case?  One warning
about SQL -- I see over and over again that SQL is used as a crutch for a
database that was poorly designed in the first place.  IBM has DRAMATICALLY
improved SQL performance, but it's still no excuse for not designing the
database properly.

>  Build libraries using the SQL command CREATE COLLECTION instead of   
>  CRTLIB.

Why?

>  Learn about journalling.  Learn about journals, journal receivers, and   
>  techniques for backing them up.

Good idea, but IMHO most shops still cannot afford the overhead.

>  Learn about Referential Integrity.  How to install it in each database.   
>   How do I handle the exceptions in RPG when I violate RI?  Why RI offers
  
>  400 database protection superior to manually coding RI in your RPG   
>  programs like some CASE tools do.  (Think client server!)  People, by   
>  manually coding RI I meant why write code to check detail files prior to
  
>  deleting the master file record when you can check for an exception on   
>  the delete statement.

Has this gotten better?  We went "bleeding edge" with an application on V3R1,
but could only receive a generic "RI failed" message.  The file status data
structure and everything else we tried rendered the same results.

>  Learn about triggers.  I've worked with people who've got enamoured with
  
>  using them for RI - they aren't getting the point.  Use RI for RI.  Use   
>  triggers for things like:  when a client adds a record to the transaction
  
>  file the 400 trigger can determine whether to fax out an acknowledgement
  
>  right away.  Again, this is a shift away from putting this code into   
>  green screen, or, batch program on your 400.  But you can see the   
>  flexibility when one migrates into client server.

Agreed, triggers are not to be used for RI.  They are, however, GREAT for
interfaces and audit (if you cannot afford journaling) purposes.

<<snip>>
>  I've long been a critic of companies (I worked for one!) that put
>  the PC-based "database du jour" in the hands of employees with a
>  semester of DBase, expecting them to whip up a new database with
>  important business data.
<<snip>>

JMHO,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"Great moments in science:  Einstein discovers that time actually IS money."
-- Gary Larson, "Far Side" caption.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *