Basic Database Design - Confirming my Learning

[robbeh]

I know there are a million threads and articles on this that I have read but I just want to confirm my learnings.

When building a database, is the idea to try and break the data into groups and multiple tables. For example, if I was making a hockey player database.

Each player would have their own table with information and stats, certain stats/options (example: positions) would have a table with a list of posistions. Then if I wanted to make a master table of players and their stats I would call on each players table help create the master table?

I think I am over thinking this one because I have read so much. If there is a good thread or article on database design/relationships please feel free to drop a link.

Thanks a lot,
Robb

[amrut]

This site has many database models. http://www.databaseanswers.org/data_models/
This one should be useful to you. http://www.databaseanswers.org/data_...ball/index.htm

[ssanfu]

Nope, that would be an unworkable design. In your example of hockey players, if there was a table for EACH player on the team, you would have upwards of 15 tables to maintain... (depending on the number of players on a team)


There should be one table for player names and a second table for stats plus other auxiliary tables.
Here are a couple of tutorial sites:
http://www.accessmvp.com/strive4peace/Index.htm
http://www.rogersaccesslibrary.com/forum/forum46.html

Here is ONE reference on table and field naming conventions:
http://www.granite.ab.ca/access/tablefieldnaming.htm

Also, Google "field naming conventions" for more examples.