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

On 2/27/2017 12:06 PM, JRusling@xxxxxxxxxxx
wrote:

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?

If you're talking about a vendor database, Joe Pluta's advice is tops.

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.

Build some views/logical files which do several things:
1) Create a 'data warehouse' effect - one place where all the bits and
bobs come together. Name the views using plain language like
Customer_Sales_History.
2) Rename various columns to something meaningful. So CUSCLS becomes
Customer_Sales_Rank.
3) Get rid of 'code' and 'status' columns and replace them with plain
language. So instead of '...where itmsts in ('3', '7', 'A', '$',
'U')...' you'd have 'where item_status = 'IN STOCK')' You could create
a 'code explanation table' and JOIN to that instead of using CASE.