Hi all,
I would like some advice on designing a Database for the HR Department. This database would primarily track employee info and their salary info.
A little history:
Recently I've been tasked with developing a database system to track info in the Human Resources Department of my company. Apparently, I wow'ed the leaders of the company by putting together an ad-hoc database that was able to make an individualized report of each employee's compensation analysis. I was able to put together all the datapoints that were formally stored in seperate Excel spreadsheets, but in haste, I crammed all data into one table, without any normalization.
Now, they want this database to continue to put out that Employee Compensation Analysis for each year in the years to come. They also want to be able to get simple mass-mailings address listings for mail-merge or label printing options. I can only imagine the potential of where this can go if it gets set up the right way.
I was wondering if any of you know of where I can find resources to read up on how to organize the data structure. I'm dealing with static data (Employee info) and time-specific data (yearly salary info)
I don't know what else I might run into, and until I hear from the HR director, I won't know, so I'm doing some preemtive research to prepare myself.
Specifics:
[ul][li]What possible types of tables would I be setting up (in general)[/li]
[li]What are some naming conventions (what would I name the database and its entities... I'm kinda stuck in a paradigm that if I name my structures well, I design well.. sometimes I get brain-blocked with just coming up with a naming convention)[/li]
[li]Are there any canned structures/flowcharts out there I can use?[/li][/ul]
Earnie Eng
I would like some advice on designing a Database for the HR Department. This database would primarily track employee info and their salary info.
A little history:
Recently I've been tasked with developing a database system to track info in the Human Resources Department of my company. Apparently, I wow'ed the leaders of the company by putting together an ad-hoc database that was able to make an individualized report of each employee's compensation analysis. I was able to put together all the datapoints that were formally stored in seperate Excel spreadsheets, but in haste, I crammed all data into one table, without any normalization.
Now, they want this database to continue to put out that Employee Compensation Analysis for each year in the years to come. They also want to be able to get simple mass-mailings address listings for mail-merge or label printing options. I can only imagine the potential of where this can go if it gets set up the right way.
I was wondering if any of you know of where I can find resources to read up on how to organize the data structure. I'm dealing with static data (Employee info) and time-specific data (yearly salary info)
I don't know what else I might run into, and until I hear from the HR director, I won't know, so I'm doing some preemtive research to prepare myself.
Specifics:
[ul][li]What possible types of tables would I be setting up (in general)[/li]
[li]What are some naming conventions (what would I name the database and its entities... I'm kinda stuck in a paradigm that if I name my structures well, I design well.. sometimes I get brain-blocked with just coming up with a naming convention)[/li]
[li]Are there any canned structures/flowcharts out there I can use?[/li][/ul]
Earnie Eng