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 |
|
zippy
Yak Posting Veteran
69 Posts |
 Posted - 2001-10-15 : 04:48:20
|
| Hi,I am developing a database of computer systems (systems are listed by users).The design I have come up with at the moment looks like this,There is a table which stores basic infomation about the system (cpu coments userid etc.)There are then a whole bunch of other tables which are linked to this one by the systemid (an identity column)Each of these tables contains information on either hdd's memory video cards etc.I also have a table of manufacturers, and a table of categories (list of parts, motherboard hdd etc.), and a table which links which manufactureres make which categories.do you follow?The only way i currently identify what is in each of the tables which is linked to the systems table is by the name of the table (eg motherboards or memory).My question is this, should I put a categoryid into each of the tables to link it to the appropriate category?I'm not sure why I would need/want to do that at the moment, I am just wanting to come up with a decent design and thought that I should consider this.I have a reason for not doing this,the column containing the categoryid would be a list of the same number - no point storing redundant data right?But when I look at my database diagram and see all these tables that are not linked to which category they are it makes me wonder if im doing this right.I can't store all the data in one table as it does not follow a regular format.Any suggestions are really appreciated :)ThanksDerekCheck out the worlds fastest computers at http://www.ocgurus.com |
|
|
|
|
|
Database design Q