EDN Admin
Well-known member
<font size=2>Hi,</font>
<font size=2>I am trying to design a database for an IT Asset Tracking Management system and so far have added these example tables. I just want to know whether the design is ok or needs to be improved as I am trying to break my tables down as much as possible. The aim is not to store too many ID values in the main tables.</font>
<font size=2> <u>Make table </u> </font>
<font size=2>MakeID (int),</font><font size=2>Make (varchar)</font>
<font size=2>(This table will store values such as HP,Dell,Fujitsu,IBM etc)</font>
<font size=2> <u>PCModel Table</u> </font>
<font size=2>PCModelID (int), </font><font size=2>MakeID (int), </font><font size=2>PCModelTypeID (int),PCModel (varchar)</font>
<font size=2>(This table will store the models of the PC)</font>
<font size=2> <u>PrinterMake Table</u> </font>
<font size=2>PrinterMakeID (int),PrinterMake (varchar)</font>
<font size=2>(This table will store values such as HP,Epson,Canon,Brother etc)</font>
<font size=2> <u>PrinterModel Table</u> </font>
<font size=2>PrinterModelID (int), PrinterMakeID (int), PrinterModel (varchar), PrinterModelTypeID (int)</font>
<font size=2>(This table will store the printer models such as Laserjet 2300, Laserjet 4050N, Brother HL5040)</font>
<font size=2> <u>PrinterType Table</u> </font>
<font size=2>PrinterTypeID (int), PrinterTypeMakeID (int), PrinterType (varchar)</font>
<font size=2>(This table will store values such as Laserjet Printer, Inkjet Printer, Dot Matrix)</font>
<font size=2> <u>PCType Table</u> </font>
<font size=2>PCTypeID (int), PCTypeMakeID (int), PCType (varchar)</font>
<font size=2>(This table will store values such as Desktop PC, Notebook, Server)</font>
<font size=2> <u>PCInventory table</u> </font>
<font size=2>PCInventoryID (int), ModelID (int), LocationID, OperatingSystemID, HardDriveID, CPUSpeedID)</font>
<font size=2>(One of the main tables after the information is saved)</font>
<font size=2></font>
<font size=2>Regards</font>
<font size=2>Dipendra</font>
<font size=2></font>
View the full article
<font size=2>I am trying to design a database for an IT Asset Tracking Management system and so far have added these example tables. I just want to know whether the design is ok or needs to be improved as I am trying to break my tables down as much as possible. The aim is not to store too many ID values in the main tables.</font>
<font size=2> <u>Make table </u> </font>
<font size=2>MakeID (int),</font><font size=2>Make (varchar)</font>
<font size=2>(This table will store values such as HP,Dell,Fujitsu,IBM etc)</font>
<font size=2> <u>PCModel Table</u> </font>
<font size=2>PCModelID (int), </font><font size=2>MakeID (int), </font><font size=2>PCModelTypeID (int),PCModel (varchar)</font>
<font size=2>(This table will store the models of the PC)</font>
<font size=2> <u>PrinterMake Table</u> </font>
<font size=2>PrinterMakeID (int),PrinterMake (varchar)</font>
<font size=2>(This table will store values such as HP,Epson,Canon,Brother etc)</font>
<font size=2> <u>PrinterModel Table</u> </font>
<font size=2>PrinterModelID (int), PrinterMakeID (int), PrinterModel (varchar), PrinterModelTypeID (int)</font>
<font size=2>(This table will store the printer models such as Laserjet 2300, Laserjet 4050N, Brother HL5040)</font>
<font size=2> <u>PrinterType Table</u> </font>
<font size=2>PrinterTypeID (int), PrinterTypeMakeID (int), PrinterType (varchar)</font>
<font size=2>(This table will store values such as Laserjet Printer, Inkjet Printer, Dot Matrix)</font>
<font size=2> <u>PCType Table</u> </font>
<font size=2>PCTypeID (int), PCTypeMakeID (int), PCType (varchar)</font>
<font size=2>(This table will store values such as Desktop PC, Notebook, Server)</font>
<font size=2> <u>PCInventory table</u> </font>
<font size=2>PCInventoryID (int), ModelID (int), LocationID, OperatingSystemID, HardDriveID, CPUSpeedID)</font>
<font size=2>(One of the main tables after the information is saved)</font>
<font size=2></font>
<font size=2>Regards</font>
<font size=2>Dipendra</font>
<font size=2></font>
View the full article