Re: Designing a database

Well to start with, I would examine the nature of the data you want to store, it's datatype, size, ect. Follow the other reccommendations as to not repeating data across tables. I tend to use autonumber fields for keys quite often. Also, think about what data could go into "domain" tables where you have a fairly non-volitile and finite set of values, and you plan on searching on this, and don't want to risk the vagaries of a user spelling it a dozen different ways when entereing the data....for example - if you have a fixed number of locations, or computer make - i.e.Dell, Compaq, etc. Also, be sure and provide admin pages to update these domain tables...maybe next month your company starts buying ABC-brand pcs - add it to the domain table. When entereing or searching - the values in these domain tables populate drop-down listboxes - not left to chance to be entered in a text field.... Phil J. Joni Järvinen - Wandu wrote: > Hey > > I'm quite new to databases so I though I'd ask you for > some tips in designing a database. > > The db that I'm supposed to design holds information > about workstations: Motherboard (Motherboard id, # of pci slots, > agp slot etc etc.), Harddisks (Size, in what ide and master/slave, etc), > the physical location of the workstation and it's hardware configuration > etc. > > So if you could give me some tips and pointers for what tables to create > etc I would be grateful. > > TIA > > -Joni- > > -- > PHP Database Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-db-unsubscribe@lists.php.net > For additional commands, e-mail: php-db-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net