CHAPTER 1
1.1 Introduction
In the modern digital era, vast amounts of data are generated every second
by organizations, institutions, and individuals. Efficient storage,
management, and retrieval of this data is crucial for decision-making and
operational efficiency. A Database Management System (DBMS)
provides a systematic way to create, maintain, and manipulate databases.
An Advanced Database Management System (ADBMS) extends the
basic concepts of DBMS by introducing advanced data models, architectures,
constraints, and conceptual modeling techniques that support complex,
large-scale, and distributed applications.
This chapter introduces the fundamental concepts of database systems
and conceptual modeling, forming the foundation for understanding
advanced database technologies.
1.2 Purpose of Database Systems
Traditional file processing systems suffer from several limitations such as
data redundancy, inconsistency, lack of security, and difficulty in data
access. Database systems were developed to overcome these issues.
Main Purposes of a Database System
Efficient data storage and retrieval
Minimization of data redundancy
Improved data consistency
Data sharing among multiple users
Data security and integrity
Backup and recovery support
Data independence
A DBMS acts as an interface between users and physical data storage,
ensuring reliable and secure data management.
1.3 Data Models
A data model defines how data is logically structured, related, and
constrained within a database.
Types of Data Models
1. Hierarchical Model
Data is organized in a tree structure with parent-child relationships.
2. Network Model
Allows many-to-many relationships using graph structures.
3. Relational Model
Data is represented in tables (relations) consisting of rows and
columns.
4. Entity–Relationship (ER) Model
Conceptual model using entities, attributes, and relationships.
5. Object-Oriented Model
Combines object-oriented programming concepts with database
systems.
The relational model is the most widely used data model in modern
database systems.
1.4 Schemas and Instances
Database Schema
A schema is the overall logical design of the database. It defines tables,
attributes, relationships, and constraints.
Schema is static
Defined using DDL commands
Changes infrequently
Database Instance
An instance represents the actual data stored in the database at a
particular moment.
Instance is dynamic
Changes frequently
Reflects current database state
📌 Analogy:
Schema is like a blueprint, while instance is the actual building.
1.5 Three-Schema Architecture and Data Independence
The Three-Schema Architecture was proposed to separate user
applications from physical data storage.
Three Levels
1. External Level
Individual user views of data.
2. Conceptual Level
Global logical structure of the database.
3. Internal Level
Physical storage details.
Data Independence
Data independence is the ability to modify schema at one level without
affecting the next higher level.
Physical Data Independence
Changes in physical storage do not affect conceptual schema.
Logical Data Independence
Changes in conceptual schema do not affect external views.
This architecture enhances flexibility, security, and maintainability.
1.6 Database Languages
Database systems support specialized languages for different operations.
Types of Database Languages
1. Data Definition Language (DDL)
Used to define database structure.
Examples: CREATE, ALTER, DROP
2. Data Manipulation Language (DML)
Used to access and manipulate data.
Examples: SELECT, INSERT, UPDATE, DELETE
3. Data Control Language (DCL)
Controls access permissions.
Examples: GRANT, REVOKE
4. Transaction Control Language (TCL)
Manages transactions.
Examples: COMMIT, ROLLBACK, SAVEPOINT
1.7 Database Architecture
Database architecture describes how database systems are designed and
deployed.
Types of Database Architecture
1. Single-Tier Architecture
Database and application on the same system.
2. Two-Tier Architecture
Client directly interacts with database server.
3. Three-Tier Architecture
Client → Application Server → Database Server
Three-tier architecture is widely used in web-based applications due to
better security and scalability.
1.8 Classification of DBMS
DBMS can be classified based on data model and architecture.
Based on Data Model
Hierarchical DBMS
Network DBMS
Relational DBMS
Object-Oriented DBMS
Object-Relational DBMS
Based on Architecture
Centralized DBMS
Distributed DBMS
Parallel DBMS
1.9 Relational Database
A relational database stores data in the form of relations (tables).
Key Components
Relation (Table)
Tuple (Row)
Attribute (Column)
Primary Key
Foreign Key
Relational databases support data integrity, normalization, and SQL
querying, making them highly reliable and scalable.
1.10 Database Users and Administrators
Types of Database Users
1. Naïve Users – Use predefined applications
2. Application Programmers – Develop database applications
3. Sophisticated Users – Write complex queries
4. Specialized Users – Develop advanced database applications
Database Administrator (DBA)
The DBA is responsible for:
Database design
Security management
Backup and recovery
Performance tuning
User authorization
1.11 Advantages of DBMS
Reduced data redundancy
Improved data consistency
Data sharing
Enhanced security
Backup and recovery
Integrity constraints enforcement
Better data accessibility
1.12 Entities and Entity Sets
An entity is a real-world object with independent existence.
Examples: Student, Employee, Course
An entity set is a collection of similar entities.
1.13 Relationships and Relationship Sets
A relationship represents an association among entities.
Examples:
Student enrolls Course
Employee works for Department
Relationship sets describe collections of similar relationships.
1.14 Keys
Keys uniquely identify entities.
Types of Keys
Super Key
Candidate Key
Primary Key
Alternate Key
Foreign Key
Composite Key
Keys ensure entity integrity and relationship consistency.
1.15 Mapping Constraints
Mapping constraints define how entities participate in relationships.
Cardinality: One-to-One, One-to-Many, Many-to-Many
Participation: Total or Partial
1.16 Constraints
Constraints restrict invalid data entry.
Types of Constraints
Domain Constraint
Key Constraint
Entity Integrity Constraint
Referential Integrity Constraint
1.17 Entity-Relationship (ER) Diagram
An ER diagram is a graphical representation of entities, attributes, and
relationships.
Components
Rectangle → Entity
Ellipse → Attribute
Diamond → Relationship
Lines → Connections
ER diagrams are used during database design phase.
1.18 Reducing ER Diagram to Tables
ER diagrams are converted into relational tables using mapping rules:
Entity → Table
Attribute → Column
Relationship → Foreign Keys or separate table
Multivalued attributes → Separate tables
1.19 Generalization and Specialization
Generalization
Bottom-up approach combining similar entities into a higher-level entity.
Specialization
Top-down approach dividing an entity into specialized sub-entities.
These concepts support inheritance in ER modeling.
1.20 Aggregation
Aggregation treats a relationship set as an entity set.
It is used when relationships themselves participate in other relationships,
enabling complex modeling scenarios.
Chapter Summary
This chapter introduced the fundamentals of database systems and
conceptual modeling. It covered database purposes, data models, schemas,
architecture, users, advantages of DBMS, ER modeling concepts, constraints,
mapping, and advanced ER features such as generalization, specialization,
and aggregation. These concepts form the backbone of database design and
advanced database management systems.