Hi All,
I am trying to come up with a database design to hold employees task information that they have completed during the week.
I am stumped at where to begin with it. Should I create a table with all the employees, a table with a list of tasks, and a table that holds the reports?
Any advice would be greatly appreciated.
Database design tips
Page 1 of 13 Replies - 841 Views - Last Post: 22 March 2011 - 03:54 AM
Replies To: Database design tips
#2
Re: Database design tips
Posted 21 March 2011 - 08:59 PM
I'd start with the employee table since its the "master" every report requires an employee to own it and every task is assigned to an employee I assume.
#3
Re: Database design tips
Posted 21 March 2011 - 09:05 PM
Quote
I am stumped at where to begin with it. Should I create a table with all the employees, a table with a list of tasks, and a table that holds the reports?
This is the route I would take. Design an Employees table to model your Employees, and a Tasks table to keep track of the work being done. Then create a linking table to relate Employees to tasks, since multiple Employees can be assigned to the same Task. I would just use the employee_id and task_id as a composite PK in the linking table.
#4
Re: Database design tips
Posted 22 March 2011 - 03:54 AM
Thanks guys, I will start there
Page 1 of 1
|
|

New Topic/Question
Reply




MultiQuote







|