Dbms Unit 2 Project.
Dbms Unit 2 Project.
PROJECT REPORT
Roll No.: 23891A67I1 Name :Surkanti Vani Branch: Data Science
Problem Statement:
Design and implement a database schema to store employee information for a large organization.
The schema should be able to store employee personal details, job information, salary details, and
benefits.
Introduction:
Concepts used :
1. Entity-Relationship Modeling (ERM): Used to identify entities, attributes, and relationships between
them.
2. Relational Database Management System (RDBMS): Implemented using MySQL.
3. Normalization: Applied to minimize data redundancy and improve data integrity.
4. SQL: Used to create and manipulate the database schema.
Database Schema Design
The following entities are identified:
Employee
Employee_ID (Primary Key): Unique identifier for each employee.
Name: Employee name.
Date_of_Birth: Employee date of birth.
Email: Employee email address.
Phone: Employee phone number.
ob
Job_ID (Primary Key): Unique identifier for each job.
Job_Title: Job title.
Job_Description: Job description.
Department: Department name.
Salary
Salary_ID (Primary Key): Unique identifier for each salary record.
Employee_ID (Foreign Key): References the Employee table.
Page 1 of 3
VIGNAN INSTITUTE OF TECHNOLOGY AND SCIENCE
(AN AUTONOMOUS INSTITUTION)
Deshmukhi (V), Pochampally (M), Yadadri Bhuvanagiri Dist., TS-508284
Implementing code:
CREATE TABLE Employee (
Employee_ID INT PRIMARY KEY,
Name VARCHAR(255) NOT NULL,
Date_of_Birth DATE NOT NULL,
Email VARCHAR(255) UNIQUE NOT NULL,
Phone VARCHAR(20) NOT NULL
);
Conclusion:
The employee database schema designed above captures essential employee information, including
personal details, job information, salary details, and benefits.
The use of entity-relationship modeling, normalization, and SQL ensures a robust and scalable database
design.
This schema can be extended or modified as needed to accommodate additional requirements or
changes in the organization's policies.
Page 3 of 3