License Compliance Database Format?
I am looking into setting up a database for software license compliance. I'm having difficulties finding a good format to follow to make the database the least confusing as possible. Can anyone help?
-Greg Gobs
IT Employment
I am looking into setting up a database for software license compliance. I'm having difficulties finding a good format to follow to make the database the least confusing as possible. Can anyone help?
-Greg Gobs
A start point is to inventory all existing software licenses. Include as a starting point any information you think you might need. At a minimum:
Inventory = name, version (may include revision information/patches applied depending upon the software), date acquired, date expires (if applicable), number of copies, where installed, serial number installed at that location, for whom
You will probably need some type of audit software that can gather information on what is installed in a given location, because this will need to be balanced against the licenses that you can locate (you may not have all the information in this instance, since organizations often lose track of such things - a guideline is to seek out the installation CDs,tally them up, and put them under lock and key.)
NOTE: most of the software audit packages have some form of DB already available, and all you would need to do in that case is enter information like purchase dates, etc.
The database if you decide to build one should be designed with every eventuality in mind - for example if your company uses block licenses, you'll need to set up your tables to allow a reference to a block license instead of an individual license.
Not the most concise answer, but hope it helps.
Clint
by g_gobs
by g_gobs
This discussion is closed to new replies.
Sort by Trending