Scribd
Upload
3 views7 pages

Lab 5

The document outlines the design and implementation of a COMPANY Database, detailing its structure, including departments, employees, dependents, project management, and work hours. It includes SQL commands to create the database and necessary tables while addressing constraints and relationships between entities. The document also emphasizes the importance of managing foreign key constraints and the order of table creation to avoid referencing issues.

Uploaded by

muhannadambon
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3 views7 pages

Lab 5

The document outlines the design and implementation of a COMPANY Database, detailing its structure, including departments, employees, dependents, project management, and work hours. It includes SQL commands to create the database and necessary tables while addressing constraints and relationships between entities. The document also emphasizes the importance of managing foreign key constraints and the order of table creation to avoid referencing issues.

Uploaded by

muhannadambon
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Lab 5

Based on the following (simplified) requirements of the COMPANY Database. We can draw an
Entity Relationship Diagram (ERD) and design a database schema.
Description of Company Database:

• The company is organized into departments.


• Each department has a unique name, a unique number, and a particular employee who
manages the department.
• We keep track of the start date when that employee began managing the department.
• A department may have several locations.
• A department controls a number of projects, each of which has a unique name, a unique
number, and a single location.
• We store each employee’s name, social security number, address, salary, sex and birthdate.
An employee is assigned to one department but may work on several projects, which are
not necessarily controlled by the same department.
• We keep track of the number of hours per week that an employee works on each project.
• We also keep track of the direct supervisor of each employee (who is another employee).
• We want to keep track of the dependents of each employee for insurance purposes.
• We keep each dependent’s name, sex, birthdate, and relationship to the employee.
Task 1: Based on the database schema design, create a new database with name
‘new_company’. Then, create all the given tables in the database scheme.
Task 2: Insert into the tables all the records in the given scheme state.
Task 1 Implementation and Notes

# Create the company database


CREATE DATABASE new_company;

# Create the database tables


USE new_company;
# Create 'DEPARTMENT' table
CREATE TABLE DEPARTMENT (
dname varchar(25) NOT NULL,
dnumber int NOT NULL,
mgrssn char(9) NOT NULL,
mgrstartdate date,
CONSTRAINT pk_Department PRIMARY KEY (dnumber),
CONSTRAINT uk_dname UNIQUE (dname)
);
/*
Notes:
1. As discussed in Chapter 4, a constraint may be given a constraint name, following the
keyword CONSTRAINT.
• The names of all constraints within a particular schema must be unique.
• A constraint name is used to identify a particular constraint in case the constraint
must be dropped later and replaced with another constraint.
• Giving names to constraints is optional.

2. A constraint NOT NULL is specified when NULL is not permitted for a particular attribute.
*/
# Create 'EMPLOYEE' table
CREATE TABLE EMPLOYEE (
fname varchar(15) NOT NULL,
minit varchar(1),
lname varchar(15) NOT NULL,
ssn char(9),
bdate date,
address varchar(50),
sex char,
salary decimal(10,2),
superssn char(9),
dno int,
CONSTRAINT pk_employee PRIMARY KEY (ssn),
CONSTRAINT fk_employee_department FOREIGN KEY (dno) REFERENCES
DEPARTMENT(dnumber)
);
/* Notes:
Here, there are some foreign keys that may cause errors:
1. The foreign key Super_ssn in the EMPLOYEE table is a circular reference because it refers
to the table itself.
To deal with this problem, this constraint will be left out of the initial CREATE TABLE
statement, and then added later (after inserting all the records) using the ALTER TABLE.
ALTER TABLE EMPLOYEE
ADD CONSTRAINT fk_employee_employee FOREIGN KEY (superssn) REFERENCES
EMPLOYEE(ssn);

2. The foreign key Dno in the EMPLOYEE table refers to the DEPARTMENT table.
To deal with this point, the table EMPLOYEE table created after creating the
DEPARTMENT table to avoid referencing a table that has not yet been created. */
# Create 'DEPENDENT' table
CREATE TABLE DEPENDENT (
essn char(9),
dependent_name varchar(15),
sex char,
bdate date,
relationship varchar(8),
CONSTRAINT pk_dependent PRIMARY KEY (essn,dependent_name),
CONSTRAINT fk_dependent_employee FOREIGN KEY (essn) REFERENCES EMPLOYEE(ssn)
);

# Create 'DEPT_LOCATIONS' table


CREATE TABLE DEPT_LOCATIONS (
dnumber int,
dlocation varchar(15),
CONSTRAINT pk_deptlocations PRIMARY KEY (dnumber,dlocation),
CONSTRAINT fk_deptlocations_department FOREIGN KEY (dnumber) REFERENCES
DEPARTMENT(dnumber)
);

# Create 'PROJECT' table


CREATE TABLE PROJECT (
pname varchar(25) NOT NULL,
pnumber int,
plocation varchar(15),
dnum int NOT NULL,
CONSTRAINT pk_project PRIMARY KEY (pnumber),
CONSTRAINT uk_pname UNIQUE (pname),
CONSTRAINT fk_project_department FOREIGN KEY (dnum) REFERENCES
DEPARTMENT(dnumber)
);

# Create 'WORKS_ON' table


CREATE TABLE WORKS_ON (
essn char(9),
pno int,
hours decimal(4,1),
CONSTRAINT pk_workson PRIMARY KEY (essn,pno),
CONSTRAINT fk_workson_employee FOREIGN KEY (essn) REFERENCES EMPLOYEE(ssn),
CONSTRAINT fk_workson_project FOREIGN KEY (pno) REFERENCES PROJECT(pnumber)
);

You might also like