Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
What's wrong with using a Summary data table?
Message
From
28/03/2013 16:04:48
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Title:
What's wrong with using a Summary data table?
Miscellaneous
Thread ID:
01569478
Message ID:
01569478
Views:
65
I'll probably get fired so saying this, but my CIO has laid down the law saying we can no longer use a summary table to get data about our members and, instead, we need to go to the "Master Data" tables.

We have almost 200,000 members and we have a lot of date sensitive layered data about the member in many different tables. Typically, we want to get the most recent layer data item like their current address - not their address five years ago.

We have a VFP table and a VFP process that summarizes some 150 fields worth of data into a summary table for the members. The process takes over an hour to run.

So, instead of one stop shopping using the summary table the CIO says we have to go to each history data table and pull the max address or whatever.

I don't see the advantage of this approach other than it will slow things down and make the code more complex.

Opinions?
Next
Reply
Map
View

Click here to load this message in the networking platform