I would try to show them the benefits of normalization....but if they don't get it, then drop it.
By the way, the insurance industry is in dire need of help. Those poor people are so used to shoving paper around that any technical savvy really shines when it comes to data management. Mike > If you are helping a company overcome "Technical Debt" would you take > take the excuse we have always done it that way instead of push > forward in a normalization way? > > I inherited a database devised back in the early 90s, I think it is > that new. Every column in a table has a prefix for it's table. In > most of the typical tables it goes to redundant columns, add1,2,3 > biz_addr1,2,3 biz_city1,2,3.... phone fax and email are all in a > similar 1,2,3 in the same ROW. > > Would you attempt to normalize this structure to Locations, People, > ContactTypes? > > In this app for billing insurance companies I have 50+ rows for > Hartford Insurance. We use 3 to bill to and 4 for claim# service > calls. The rest are "agents" who sold the policy, I think. > > > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
