System configuration table structure

[rondog]

I will begin working on a project very soon that is a System Configuration Manager. It is for a company thas has X amount of machines and this project will allow them to easily manage and search through them.

 

Most of the system properties like: System name, serial no., date installed etc are easy to manage. That is one table. The part that has got me thinking are things like Memory and CPUs where their can be more than 1.

 

My thought was to make a table strictly for memory that had a system_id that was sort of the tie back to the main system config table. Same goes for CPUs.

 

Do you guys have a better suggestion or does my idea sound about the right way to do it?

[Adam]

I would create a kind of 'attributes' table for non-standard details:

 

attr_id | machine_id | attr_name | attr_desc

---------------------------------------------------------------

1      | 1          | Memory    | Description of the memory installed

2      | 1          | CPU      | Description of the CPU installed

 

Linking to the machine by `machine_id` of course.