Results 1 to 2 of 2
  1. #1
    Join Date
    Sep 2009

    Unanswered: Looking for Suggestions

    Hi all,

    Hopefully this is the right place for this. I have inherited a project from an Athletic Directory to compile stats for the history of a High School Basketball program. He has given me all the scorebooks and they include the season year (eg: 1981-1982), the players, the players game by game statistics, and the result of each game.

    I am interested in putting together a database that I can use to access career stats for the players, coaches, etc. I have some ideas of how I want to do this and I just want to run them by others before really getting into this.

    As far as tables go, I believe I need tables for the following:

    1. Players (List of All Players who are listed in the scorebooks)
    2. Coaches (List of All Coaches who are listed in the scorebooks)
    3. 1 Table for Each Seasons Roster (20something in total)
    -So, table for the 79-80 roster, 80-81 roster, .... 07-08 roster
    4. 1 Table for Each Seasons Schedule
    -Same thing as point 3.

    Does this seem like a good start to people? Or am I missing something that would make this incredibly less complex?

    Thanks in advance for any feedback.


  2. #2
    Join Date
    Nov 2004
    out on a limb
    Provided Answers: 59
    have a look at the usual references doled out here on normalisation and table design
    Fundamentals of Relational Database Design --
    The Relational Data Model, Normalisation and effective Database Design

    first off if the only difference between ech season's 'roster' is the season then I'd expect that to be one table with a column within that table identifying which season that row applies to.
    likewise season schedule, for the same reason
    I'd rather be riding on the Tiger 800 or the Norton

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts