Company (HR)
employees who report to employees, departments, salaries and leave. 7 tables, 25 columns, no data.
The map
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
idbigintPKnamevarchar(200) requiredbudgetnumeric(12,2)
job_titles
idbigintPKnamevarchar(200) required
employees
idbigintPKfull_namevarchar(200) requireddepartment_idbigint→ departments requiredjob_title_idbigint→ job_titles requiredmanager_idbigint→ employeeshired_ondate required
salary_history
idbigintPKemployee_idbigint→ employees requiredamountnumeric(12,2) requiredfrom_datedate required
leave_requests
idbigintPKemployee_idbigint→ employees requiredstarts_ondate requiredends_ondate requiredstatusvarchar(30) required
projects
idbigintPKnamevarchar(200) requiredowner_idbigint→ employees required
project_members
project_idbigint→ projects requiredemployee_idbigint→ employees required
What you could look at in SSDO
- employees.manager_id links employees to itself: see how the Map draws it.
- Ask who reports to whom, as a question about structure.
- salary_history holds pay: Governance would describe it as sensitive-looking, never read it.
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.