Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mossman65
Starting Member
1 Post |
Posted - 2008-11-14 : 13:26:50
|
| Hello All!I have a new client that has a fairy simple .xls that i am breaking apart for it to be a drill down search: Year+Make+Model=Parts. Here is a exmple row of data:Make:ACURA Model:INTEGRA Year:1990 Engine: L4Edition: GSTrans Cooler: x=trueOil Cooler: Horse Power:0-400 Comments: Part Number:9E-HE790-01 Tube Size:1.50" Rows:1Core Size:13.00 x 26.88I have broken into the following tables: {}=colums in the tableYear: {vehicle_year}Make: {vehicle_make}Model: {vehicle_model}Vehicle_specs {cooler_type} {engine_size} {horsepower} {comments} {tube_size} {rows} {core_size}Product_id {part_number} {image_path} {image_name}Does this seem to be a solid way to design the tables?All Comments and criticism are welcomed! |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-11-14 : 23:48:54
|
| there are no linking columns. there should be a way by which you link year,make,Model,... Or else how can you distinguish which vehiclespecs record corresponds to which make and model and was made in which year. put some id columns in the tables to act as primary key and include it as foreign keys in others to link to them.something like belowYear:{year_id}pk identity{vehicle_year}Make:{make_id}pk identity{vehicle_make}Model:{Model_id}pk identity{vehicle_model}Vehicle_specs{spec_id} pk identity{cooler_type}{engine_size}{horsepower}{comments}{tube_size}{rows}{core_size}Product_id {id} pk identity{part_number}{spec_id} fk to Vehicle_specs{year_id} fk to Year{make_id} fk to Make{model_id} fk to Model{image_path}{image_name} |
 |
|
|
|
|
|