Re: Articles or links to build a case on why to improve your rpg-db2 database.

[Booth Martin <booth@xxxxxxxxxxxx>]

Experiences led me to the conclusion that a long term rewrite is 
needed.  When confronted with situations like this we would select our 
smallest, least critical application and use that for the learning 
exercise.  Usually it would be redone in a week or two at least to a 
level where it could be reviewed and commented upon. Then the fun 
began.  However, in an astonishingly short time we would have a brand 
new application that blew away the original, Then, rinse & repeat.  By 
the time we got to big, business critical applications we'd seen what we 
could do and how to do it.  Yes, it took a long time for the whole 
process but once completed we realized it really didn't take all  that 
long after all.  Not when we looked at other folk's timelines for 
conversions.


On 2/27/2017 11:06 AM, JRusling@xxxxxxxxxxx wrote:
> Our database files here leave a lot to be desired.  In our environment
> (w/o any change management tool) the trend has been to create an extension
> file with a 1 to 1 relationship with the affected file when fields need to
> be added to a affected file.
>
> ie Item master file is IIM, so let's create an XIM file that relates to
> the IIM file in a one to oen relationship, oops need more fields create an
> XIM2 extension file...
>
> If anyone has any links or articles on the benefits of cleaning up or
> normalizing or just plain improving the ERP database I would appreciate
> them.
> Any ammunition is appreciated?
>
> Also, in the past they have re-purposed file fields w/o changing the files
> to reflect the new purpose...   a lot.
>
> I would like to empower users to create their own reports but with the
> state of the database the way it is, that ain't gonna happen, heck i'm a
> programmer and i get confused with all the mislabeled fields and extension
> files.
>
> Thanks for any links or help.
>
> John
>
> v7.2
> <br />
> The information in this email is confidential and may be legally privileged.
> It is intended solely for the addressee. Access to this email by anyone else is
> unauthorized. If you are not the intended recipient, any disclosure, copying,
> distribution or any action taken or omitted to be taken in reliance on it, is
> prohibited and may be unlawful.