I'm sorry, I'm sure this is a complete n00b question, but I've been working with collecting data, and I'm starting to get to the point where I'd like to start populating a database, but I can't figure out what system will work best.

Final Project:
Dealing with TV Shows and information from the database...

TV Show
- Seasons
- Episodes in season (for episode in each season)
- Information about episode in season

What I Have To Be Able To Do
- Add various other entries into the/a database/table either spanning a certain episode or a whole season (the number of variables for each entry would variate).
- Add/update episodes or seasons for a show

My Background
I haven't dealt with front-end databases much at all; and I haven't done anything complicated with SQL before (I only know how to create databases, tables, columns, and then insert data into those columns).

Questions
(1) Is there a "right" way to do this in terms of performance? In terms of ease-of-use for the programming later?
(2) If there is a right way, what is it? If there isn't, why?
(3) What are the main considerations?
Robin Hood Reviewed by Robin Hood on . How Should I Organize My SQL Tables? I'm sorry, I'm sure this is a complete n00b question, but I've been working with collecting data, and I'm starting to get to the point where I'd like to start populating a database, but I can't figure out what system will work best. Final Project: Dealing with TV Shows and information from the database... TV Show - Seasons - Episodes in season (for episode in each season) - Information about episode in season Rating: 5