Hello Experts,
I am working on an assignment for school, which is actually completed, but the instructor left me with some "thoughts for the future", that I don't quite understand. My tables were linked and normalized quite a bit from my initial design, however tblKey_Statistics still could be normalized some more. This is what he said:
"There are still a couple of issues, but these are things that you would discover on your own with time and experience.
Specifically, Im referring to the multiple STATs tables that you created.
Technically, these are repeating groups . If you think of them as Stat1 , Stat2 , and Stat3 you might begin to see that if you decide to add yet another stat later, you would still need to change structure. In this case, you would not only add a field to KEY_STATISTICS, but you would also need to add a separate table. You are on the right track with a many to many, but one of the things that throws of students is the parent/child relationship. In our lives of course, we only have two parents, but in the database world, child entities specifically the junction tables, can have many parents.
Basically, you would have a STAT table and it would list all of the different stats you wanted to track not as fields, but as records. Then you would link this with the fund.
Your KEY_STATISTICS table would be very streamlined with KeyStatisticsId, a foreign key from your single STAT table (StatId), a key from FUND, and the Date."
So I guess that rather than fields, the Stats would be records, and hence the junction table, but I do not understand how to implement this.
Attached are two versions (version 1, was what I turned in, prior to the advice) and (version 2, is what I started to work on, but couldn't figure it out).
Kevin
Start Free Trial
