Create a manageable database

[mjsel]

I have an employee database that has way too many columns in it. In fact, soo many that I cannot add another. I need to figure out a way to break the information up but still be able to easily manage the data. I have been using queries to find the data I need but I know that there has to be a better way to house the info.



The database houses: pay, training, benefits, evaluation, and general data like address, etc. Should I create seperate tables for the specific areas ie Benefits, Pay, etc?

Also, is there a way to link two tables together so that information will auto-populate? Ex: I have an Employee table and a Benefits table. I want to be able to have the FirstName and LastName from Employee table to carry over into Benefits table as to not create duplicate entry. Is there a way to do so if it is linked to a primary key (EmpId)?

Sorry for the book and thanks for your help. -M

[dcrake]

It seams to me that you need to normalise your database. Seldom have I seen systems that run out of resources. Using primary and foreign keys is the route to take so that data is cascaded through without the need for duplication. what does you relationships look like?

David