September 3, 2006 at 2:38 am
Was wanting to get some ideas for design on a database I would like to create.
I want to store PC inventory such as hardware and software in this database and be able to update it often.
The hardware is probably not such an issue for me but the software I'm not sure how to handle it.
There could be from say 20 to 400+ applications installed with many that are very close or exact in name but typically will have a path or version number that is different.
It doesn't seem prudent to dump all the software into a single column as then it would probably take a complex query to get back specific deatails as well as it might take a long time to run the query.
I want the database to be similar to SMS (Systems Management Server) though not as complex, in that I want to store inventory and report on inventory.
As usual with everyones desires I want the database to operate effeciently and quickly.
Thanks for any ideas, suggestions.
September 3, 2006 at 5:26 am
Well I don't really know what you need to keep so I'll refrain to only the software problem.
You could always have a Softwares table (SoftwareID identity(1,1) PK Clustered, SoftwareName (Unique)).
Then the InstalledSoftwares table could look something like this :
PcID (indexed only)
SoftwareID (unique key with Version)
Version (unique key with Version)
InstallPath
...
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply