I've done some real basic DB work in mySQL. Now, however, I'm working on a project at work using MS SQL and is a little more complex than I've worked with before. So, I guess my message here is I'm pretty new yet.
My question is about design and the best way to layout some tables. I'm working on a online phone directory for 2 hospitals. Here is what I have now
You need to establish a "many-to-many" relationship between employees and departments using a third table. The natural, unique key of this table ("EmployeeDepartments") would be the primary keys from Employees and Departments.
Any reason you are choosing to mix two distinct naming conventions in your design? That's bound to prove annoying at some point.
If it's not practically useful, then it's practically useless.
You might, also, consider an employee phone table (emp_id, phone_type (i.e.ager mobile, etc...) phone_num (possibly split up by area code/prefix, etc...)), same for the department. As an employee may or may not have a pager AND a mobile, or none of them, could even have multiple land lines to one employee.