|
|
Posted by Erland Sommarskog on 10/01/12 11:27
calan (none@nospam.com) writes:
>> What is the purpose of all these input tables?
>
> This is basically an engineering configurator for a very complex product.
> Each input table holds data for a specific "component" of the product.
>
> Using the analogy of a car, a table called "Interior" may have fields
> such as "Seat Color", "Stereo Type", "Number Of Speakers", and maybe
> tens or hundreds more... A Suspension table could have "Wheel Size",
> "Spring Type", "Load Rating", "Brake Type", etc etc.
>
> If you have 100 components with maybe 30-50 configuration questions for
> each one..and then multiple products tied into the same system......
> well.... you end up with a massive number of input fields in one table
> to say the least... Also, I need the ability to work on individual
> components with seperate apps, so the multiple table approach seemd to
> make sense.
OK. To be perfectly honest, I still have a kind of feeling that the
arrangement is not the best. But I would have to looking into business
requirements etc to tell for sure. But that would maybe then be
with the placement of all these Congifured flags. Having separate tables
certainly makes sense, since else you would get a very wide table, as
I understand it.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Navigation:
[Reply to this message]
|