Database Schema

I am developing a database to manage faculty and staff.  However, I am having some trouble.  Below is a sample schema that I am working on.  Any feedback would be greatly appreciated.  My concern is that I have an employee table and I have a faculty table, should the two tables be merged even if everyone that is a staff member is not a faculty member.  

Thank you.
Who is Participating?
Chris LuttrellConnect With a Mentor Senior Database ArchitectCommented:
The only issue I see with your schema diagram is that it appears that you have a one to many relation between Employee and Faculty_Info, unless that is some kind of slowly changing dimension ,which would require a date component in the key, it should be a 1 to 0 relation where the EmployeeId is both the primary key in Faculty_Info and the foreign key to point back to Employee.  I have used this model in the database to mimic inheritance in objects where you want to represent that a Faculty_Info object "Is A" Employee object.
Patrick MatthewsCommented:
The faculty table seems redundant: wouldn't that "role" table indicate faculty vs other staff types?
shanemayAuthor Commented:
Right it would indicate the role, however, if they are also faculty member then additional information needs to be gathered (office hours, title, etc...). Information that other staff members will not have or need.
shanemayAuthor Commented:
Thank you for the feedback.  
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.