Lecture Constraints type scenario:

1. Unique Constraint

Scenario: A company is maintaining a database for its employees. Each employee must have a
unique email address, as it is used for communication and identification.

Question: How would you implement a unique constraint for the email addresses, and what would
happen if a duplicate entry is attempted?

Solution:

 Implementation: In the Employees table, you would define the Email column with a unique
constraint:

sql
Copy code
CREATE TABLE Employees (
EmployeeID INT PRIMARY KEY,
Name VARCHAR(100),
Email VARCHAR(100) UNIQUE
);

 Outcome: If a user attempts to insert an employee with an email that already exists, the
database will reject the operation and return an error, ensuring that all email addresses
remain unique.

2. Foreign Key Constraint

Scenario: A school database has two tables: Students and Enrollments. Each enrollment record
must reference a valid student.

Question: How would you set up a foreign key constraint, and what would happen if someone tried
to enroll a student who does not exist in the Students table?

Solution:

 Implementation: In the Enrollments table, you would define the StudentID column as a
foreign key:

sql
Copy code
CREATE TABLE Students (
StudentID INT PRIMARY KEY,
Name VARCHAR(100)
);
 CREATE TABLE Enrollments (
EnrollmentID INT PRIMARY KEY,
StudentID INT,
CourseID INT,
FOREIGN KEY (StudentID) REFERENCES Students(StudentID)
);

 Outcome: If an attempt is made to insert an enrollment record with a StudentID that does
not exist in the Students table, the database will prevent the operation and raise an error,
preserving referential integrity.

3. Check Constraint

Scenario: A financial institution needs to ensure that all account balances in its database are non-
negative, as negative balances are not allowed.

Question: How would you implement a check constraint for account balances, and what would
happen if someone tried to insert a negative balance?

Solution:

 Implementation: In the Accounts table, you would define a check constraint on the Balance
column:

sql
Copy code
CREATE TABLE Accounts (
AccountID INT PRIMARY KEY,
AccountHolder VARCHAR(100),
Balance DECIMAL(10, 2) CHECK (Balance >= 0)
);

 Outcome: If a user tries to insert or update an account with a negative balance, the
database will reject the operation and return an error, ensuring that all account balances
are valid.

4. Not Null Constraint

Scenario: A project management application has a Projects table where each project must have a
name and a start date.

Question: How would you enforce that the ProjectName and StartDate columns cannot be null?

Solution:
  Implementation: In the Projects table, you would define the ProjectName and StartDate
columns with the NOT NULL constraint:

sql
Copy code
CREATE TABLE Projects (
ProjectID INT PRIMARY KEY,
ProjectName VARCHAR(100) NOT NULL,
StartDate DATE NOT NULL
);

 Outcome: If someone tries to insert a project record without specifying the project name or
start date, the database will reject the operation, ensuring that all projects have the
necessary information.

5. Default Constraint

Scenario: A library management system needs to assign a default status to new books when they
are added to the Books table, indicating that they are available.

Question: How would you set up a default constraint for the Status column?

Solution:

 Implementation: In the Books table, you would define the Status column with a default
value:

sql
Copy code
CREATE TABLE Books (
BookID INT PRIMARY KEY,
Title VARCHAR(200),
Author VARCHAR(100),
Status VARCHAR(10) DEFAULT 'Available'
);

 Outcome: When a new book is added without explicitly specifying the status, it will
automatically be assigned the value 'Available', simplifying data entry and maintaining
consistency.
Component of Database Scenario:

Scenario: Hospital Management System

Imagine a hospital that needs a comprehensive system to manage patient records, appointments,
treatments, billing, and staff interactions. The system must handle multiple users, including doctors,
nurses, administrative staff, and patients.

Question: Identify and explain the components of the database system involved in this
hospital scenario.

Components of the Database System:

1. Hardware
o Role: The physical devices that host the database and run the necessary
applications.
o Example:
 Servers: High-performance servers to host the database and application
software.
 Storage: Reliable storage solutions (e.g., SSDs) to ensure fast access to
patient records and other data.
 Network Equipment: Routers and switches to facilitate communication
between users and the database.
o Explanation: Reliable hardware is critical for ensuring the system can handle
simultaneous access from multiple users, especially during peak hours (e.g.,
emergency admissions). Proper hardware setup minimizes downtime and latency,
enhancing overall efficiency.
2. Software
o Role: The applications and database management systems (DBMS) that facilitate
data storage, retrieval, and management.
o Example:
 DBMS: A system like MySQL, PostgreSQL, or Oracle Database to manage the
data.
 Application Software: A web-based application for staff and patients to
access the system.
o Explanation: The software enables data management, provides user interfaces, and
handles business logic. A robust DBMS ensures efficient data operations, while user-
friendly applications make it easy for staff and patients to interact with the system.
3. Data
o Role: The information stored in the database, including patient records,
appointments, medical histories, billing information, and staff details.
o Example:
 Tables: Patients, Appointments, Doctors, Treatments, Billing.
o Explanation: Accurate and well-structured data is crucial for delivering quality
healthcare. The database must be designed to ensure data integrity, consistency, and
accessibility, allowing healthcare providers to make informed decisions quickly.
4. Procedures
o Role: Defined operations that encapsulate business logic for data manipulation,
often implemented as stored procedures in the DBMS.
 o Example:
 A stored procedure for registering a new patient that checks for duplicates,
validates input, and inserts data into the Patients table.
o Explanation: Procedures simplify complex operations, enhance security by hiding
underlying SQL code, and ensure data integrity by enforcing business rules
consistently.
5. Modularity
o Role: The design principle of dividing the system into distinct components or
modules that can be developed and maintained independently.
o Example:
 Separate modules for Patient Management, Appointment Scheduling, Billing,
and Medical Records.
o Explanation: Modularity makes the system easier to develop and maintain. Teams
can work on different modules concurrently, allowing for parallel development and
testing. It also enhances flexibility, enabling quick updates or changes to specific
components without affecting the entire system.
6. Reusability
o Role: Designing components or procedures that can be utilized in multiple contexts
without modification.
o Example:
 A function for validating patient data (e.g., checking date formats) that can
be reused across patient registration and appointment scheduling.
o Explanation: Reusability reduces redundancy and accelerates development. It
ensures that common functionalities are consistent across the system, which
simplifies maintenance and enhances reliability.
7. Transaction Management
o Role: Ensures that all database transactions are processed reliably, adhering to
ACID properties (Atomicity, Consistency, Isolation, Durability).
o Example:
 When a patient schedules an appointment, the system must ensure that the
appointment is created, the doctor's schedule is updated, and any necessary
notifications are sent in a single transaction.
o Explanation: Effective transaction management is critical for maintaining data
integrity, especially in a hospital environment where simultaneous updates can
occur. It ensures that incomplete operations do not leave the database in an
inconsistent state.
8. People (Users)
o Role: The individuals who interact with the database system, including healthcare
professionals, administrative staff, and patients.
o Example:
 Roles: Doctors who access medical records, nurses who update patient
statuses, and administrative staff who manage billing.
o Explanation: Understanding user roles and their specific needs is essential for
designing an intuitive interface and implementing security measures. Role-based
access ensures that sensitive patient data is only accessible to authorized personnel,
maintaining confidentiality and compliance with regulations.