Question Designing and building my first database

[Vector891]

Hi,

So I have been given the project of designing an Asset Management database for the company I work for. Being that I have not designed a database before since Uni, I'm not sure the best way to design a database of this size.

Ideally this database has to hold Asset Information ie, AssetID,AssetDescription,ModelNumber,Make,SerialNumber,EmployeeID,Location,Purchase cost, current value, depreciation life, and Asset category(computer equipment,office equipment,fixtures) and then asset type ( computer,monitor,desk) etc. Something I did have a slight issue with is with regards to the asset category and asset type, as Ideally what the company want to have is that each asset is assigned to a category and a type, so that in a dropdown box you will select the asset category, in this case lets say ComputerEquipment and then below that have a drop down with only the asset type that relates to computer equipment. How would be best to design something like this? and is there any pitfalls that I need to be sure to avoid?

Thanks if anyone can provide any info

 

[spikepl]

Hone your google skills: nowadays most things have been dealt with by others and no point reinventing the wheel.


For example, check out all the free templates at microsoft. Here is one: http://office.microsoft.com/en-us/templates/desktop-asset-tracking-TC001225342.aspx


A reality check: millions of companies manage assets without developing own db to do it - what is the justification for this? As training - fine. As a tool, why not buy exisitng verified off-the-shelf stuff? Or is the company not paying for your time?

 

[Vector891]

Thanks for the link I will look into that template.

My company don't really want to spend the money on a prebuild product. We are an IT company and the CEO asked my manager to build this, and my manager delegated this to me.

 

[jdraw]

Here is a tutorial that may help with a first database. It leads you through the process of defining the "things'(entities) involved and how they relate to each other (relationships). It will help you with putting the concepts of database design in context.
You can use the skills you learn in building your database.