I look at an automotive sales report each month that lists number of cars sold by brand. The hierarchy of this data is as such:
Parent company -> Make -> Type -> Model
One 'parent company' (ex. GM) will have many 'makes' (ex Buick, or Cadillac, or Chevrolet, etc). One 'make' has one of two 'types' (car or truck), and for each type there are several models (1 Series, 3 Series, etc).
Each month I would like to add the new sales data when the report is issued.
I am wondering if I should create a new table for each parent company, and in the table have fields 'Make', 'Type', 'Model' and 'Sales'. Is this the most logical and efficient way to structure this data?
Any suggestions are more than welcome. I appreciate the help in advance.
Thank you for the quick reply. So should I create the rows 'id', 'parent company', 'make', 'type', 'model', 'date' and 'sales' and create a new column each time the monthly data is released (to update the 'date' and 'sales' values)?
Much of the data will be the same every single month - 'parent company', 'make', 'type', and 'model' will never change. Is there a better way to structure this information, or is the way stated above the best for this type of job?
And, No. Do NOT create a new column each time a month is added. That would be a big mistake. Include the month in the table definition, and add a new record with the month and the sales data.
"Lisa, in this house, we obey the laws of thermodynamics!" - Homer Simpson
"I have my standards. They may be low, but I have them!" - Bette Middler
"It's a book about a Spanish guy named Manual. You should read it." - Dilbert