Although this is a real newbie question, I think a little guidence is all I need to get going on my own..
I'm designing a program to track and analyize budget allocations for multiple projects across multiple categories. For example:
Project 1: New York
Categories: Print, TV, Radio, etc.
Project 2: Los Angeles
Categories: Print, TV, (can be same as project 1)
Within each category is multiple campaigns, for exmaple, in TV for New York:
ABC
NBC
etc.
And within each campaign are multiple data I need to track:
ABC Coupons: ABC1, ABC2
ABC Coupon uses: ABC1 had 10 uses, ABC2 had 20 uses
How do I structure my DB to contain all this data. I'm having some trouble wrapping my head around it.. for example, do I need a DB for each project and a table for each category with a field for each campaign? Or can I use 1 db with a table for each project, a field for each category... and then.. what?
Thanks for your help,
Jon
A newbie question
Moderator: General Moderators
- feyd
- Neighborhood Spidermoddy
- Posts: 31559
- Joined: Mon Mar 29, 2004 3:24 pm
- Location: Bothell, Washington, USA
Here's what I can see
Basic Tables
Projects
Categories
Campaigns
Coupons
Basically, you have a table for each "type" of data you have, in a general sense, not necessarily specific.
Then there are linking tables when there is many-to-many relationships between types. For instance, between Projects and Categories, there can be many Projects that are associated with many Categories.
Something to research:
http://en.wikipedia.org/wiki/Database_normalisation
Basic Tables
Projects
Categories
Campaigns
Coupons
Basically, you have a table for each "type" of data you have, in a general sense, not necessarily specific.
Then there are linking tables when there is many-to-many relationships between types. For instance, between Projects and Categories, there can be many Projects that are associated with many Categories.
Something to research:
http://en.wikipedia.org/wiki/Database_normalisation