Company (HR)

employees who report to employees, departments, salaries and leave. 7 tables, 25 columns, no data.

The map

Map of the 7 tables and their linksN1N1NN1N1N1N1N1departmentsPKidbigintnamevarcharbudgetnumericjob_titlesPKidbigintnamevarcharemployeesPKidbigintfull_namevarcharFKdepartment_idbigintFKjob_title_idbigintFKmanager_idbiginthired_ondatesalary_historyPKidbigintFKemployee_idbigintamountnumericfrom_datedateleave_requestsPKidbigintFKemployee_idbigintstarts_ondateends_ondatestatusvarcharprojectsPKidbigintnamevarcharFKowner_idbigintproject_membersFKproject_idbigintFKemployee_idbigint

Each line runs from a linking column (N) to the key it points at (1). The same tables are listed below as text.

The tables

departments

  • id bigintPK
  • name varchar(200) required
  • budget numeric(12,2)

job_titles

  • id bigintPK
  • name varchar(200) required

employees

  • id bigintPK
  • full_name varchar(200) required
  • department_id bigint→ departments required
  • job_title_id bigint→ job_titles required
  • manager_id bigint→ employees
  • hired_on date required

salary_history

  • id bigintPK
  • employee_id bigint→ employees required
  • amount numeric(12,2) required
  • from_date date required

leave_requests

  • id bigintPK
  • employee_id bigint→ employees required
  • starts_on date required
  • ends_on date required
  • status varchar(30) required

projects

  • id bigintPK
  • name varchar(200) required
  • owner_id bigint→ employees required

project_members

  • project_id bigint→ projects required
  • employee_id bigint→ employees required

What you could look at in SSDO

Create a free workspace and open this sample   All samples

PK is a primary key. “→ table” is a link (a foreign key) to that table. This page is a description of a structure we wrote; it holds no rows.