CS2003 Database Management Systems
(Database Design and Management)
August 4-5, 2025
Dr. Pritee Khanna
Professor, Computer Science & Engineering
pkhanna@[Link]
Why this course?
Databases are Everywhere
◼ You're using a Database
System if you ...
– Transfer money
– Shop on Amazon/Myntra…
– Book a train/flight ticket
– Enroll in a course
– ...
2
Why this course? Involve both
art and
Enjoyable, engineering
interesting, &
challenging Transforming
those designs
Understanding into physical
user databases with
requirements functionally
and translating complete, high
them into performance
effective applications is
database an engineering
designs is an process
May lead you to one of
artistic process the hottest career paths
3
Database Processing
◼ Always been an imp topic in the study of information
systems
◼ Modern businesses and financial systems heavily
depend on databases systems and transaction
processing for their successful operation.
◼ Enables organizations to use data to fulfill customer
needs, support business operations, and provide
valuable insights for management.
◼ Databases - backbone of all major applications today
◼ Industry Support
4
Objectives
◼ Raise awareness about databases, database
design and database management systems
◼ Enable you to design and use a database to
support an application
◼ To understand the implications of your design
◼ To realize that designing databases is non-
trivial and requires imagination, flexibility and
thought
5
Course Structure
◼ Concept of Data and Database Management Systems;
◼ Database System Architecture;
◼ Entity Relationship Modeling and Design;
◼ Relational Model: Algebra, Calculus, Normal Forms;
◼ Structured Query Language;
◼ Transaction Processing: Concurrency Control and
Recovery;
◼ Database Security and Authorization;
◼ Storage Structure and File Organization; and
◼ Introduction to Client-Server & Distributed Databases
6
Texts
Many classic textbooks (each of them will do it)
◼ Elmasri, Navathe, Somayajulu, Gupta, “Fundamentals
of Database Systems,” Pearson Education (Textbook)
◼ Kroenke D. M., “Database Processing Fundamentals,
Design, and Implementation,” Pearson Education
◼ Raghu Ramakrishnan and Johannes Gehrke,
“Database Management Systems,” McGraw Hill Higher
Education
◼ Silberschatz A., Korth H. F., Sudarshan S., “Database
System Concepts,” McGraw-Hill.
◼ Date C. J., Kannan A., Swamynathan, “An Introduction
to Database Systems,” Pearson Education
7
Grading Scheme
◼ Assignments: for your practice
◼ Quizzes: 10%
◼ Mid Sem: 20%
◼ End Sem: 40%
◼ Lab: 20%
◼ Project: 10%
– Submission and Approval of Topic
(group of 5 students → fill in Google form shared
by course TA with at least 2 topics (with at least
5 modules) - Aug 20, 2025)
– Discussions/Presentations and Final Product 8
◼ Course webpage:
Drive link will be shared
◼ Course TA:
Ms. Sudha Singh
22pcso03@[Link]
9
File-Processing Systems
Customer Customer
Customer Processing file user
file Application(s)
Order Order file
Order Processing user
file Application(s)
10
File-Processing Systems
◼ Limitations:
1. Data are separated and isolated
2. Much data is duplicated
3. Application programs are dependent of file
formats
4. Files are often incompatible with one another
5. It is difficult to represent data in the user’s
perspectives
11
1. Data are separated and isolated
◼ Example: a marketing manager needed to relate sales
data to customer data
◼ The data need to be extracted somehow from the two
files and combined into a third file
◼ With file processing it is difficult
– First, system analysts and computer programmer must
determine which parts of each of the files are needed
– Then they must decide how the files are related to one
another
– Finally, they must coordinate the processing of the files
so that the correct data are extracted
12
2. Data Duplication
◼ The most serious problem with duplicated data
concerns data integrity
◼ A collection of data has integrity if the data are
logically consistent
◼ Data duplication often results poor data integrity
◼ Data integrity problems are serious
◼ When results are inconsistent, the credibility of the
stored data, and even the MIS function itself, comes
into question
13
3. Application Program Dependency
◼ With file processing, application programs depend
on the file formats
◼ Usually in file processing systems physical formats
of files and records are part of the application code
◼ Ex: pin code field from 6 to 9 digits
– All programs using the customer record must be modified,
even if they do not use the pin code field
– Need to identify all the affected programs, modify them,
and then retest them
◼ Requiring programmers to modify programs that do
not use the field whose format has changed is a
waste of money
14
4. Incompatible Files
◼ One consequence of program data dependency - file
formats depend on the language or product used to
generate them
◼ The format of a file processed by a program is
different from the format of a file processed by other
program.
◼ As a result, files cannot be readily combined or
compared
◼ Need to convert both files to a common structure
before we could combine the records
◼ Time consuming and difficult
15
5. The Difficulty of Representing
Data in the Users’ Perspective
◼ Example: Representation of a customer invoice
– Invoice: a fixed length heading + a variable length
body
– Invoice: variable length object: The number of lines
printed on the invoice depends on the number of
purchases the customer made
◼ Interleaving two types of records is difficult to
process in application programs
16
Database Processing Systems
◼ To overcome the limitations of file processing systems
◼ This is accomplished by adding a new component, the
database management system (DBMS)
Customer Customer
Processing file user
Application(s)
File Defn
Order file
Customer data Order
user
Order data DBMS Processing
Other data Application(s)
Other
Other user
Application(s)
17
DBMS: A Logical Interface
University Database Lab
Timetable
Data
Database Teaching
course Mgmt Schedule
student System
lecturer
Tutorials
Data Dictionary
University ?QUERIES
or
Database
System Catalog
Metadata
significant
difference
◼ The DBMS is a (set of) program(s) that processes the database
18
Database Processing Systems
◼ Makes application programming easier
◼ The DBMS is a program (or, a set of programs)
that allows
– stored data to be integrated
– reduces data duplication
– ensures data integrity
– eliminates program dependency on file formats, and
– allows complicated objects to be easily represented
and retrieved
19
Integrated Data
◼ All the application data are stored in a single
facility: database
◼ An application program can ask the DBMS to
access customer data or sales data or both
◼ Application programmer specifies only how the
data are to be combined, and the DBMS
performs the necessary operations to do it
◼ Thus, the programmer is not responsible for
writing programs to consolidate the files, as
must be done for file processing system
20
Reduced Data Duplication
◼ Minimal duplication of data
◼ For example: customer no., name, address
are stored only once
◼ Whenever these data are needed, the DBMS
can retrieve them
◼ Whenever they are modified, only one update
is necessary
◼ Benefits of storing data at one place only
– Data integrity problems are less common
– Less opportunity for discrepancies among multiple
copies of the same data item 21
Program / Data Independence
◼ Reduces the dependency of programs on file formats
◼ All record formats are stored in the database itself
along with the data, and they are accessed by the
DBMS, not by application programs
◼ Now application programs need not include the
format of all the files and records they process
◼ Application programs must contain only a definition
(length + data type) of each of the data items they
need from the database
◼ The DBMS maps the data items into records and
handles other similar transactions
22
Easier Representation of the
Users’ Perspective
◼ Database technology makes it possible to
represent, in a straightforward fashion, the
objects found in the user’s world
◼ It is possible because the relationships
among the records of data are stored as part
of the database
23
Database
◼ A database is a self-
describing collection of
integrated records
24
A database is self-describing
◼ Users’ data + description of its own structure
◼ Data dictionary, data directory, or meta data
◼ Self-describing characteristic - Importance
– Promotes program-data independence
❖ Possible to determine the structure and content
of the DB by examining the DB itself
– In case of change in the structure of the data:
❖ Enter only that change in the data dictionary
❖ Only those programs that process the altered
data items must be changed
25
Database contains more than the
files of user data
Standard hierarchy of data Files
+
Bytes Metadata
Bits Or Fields Records Files+
Indexes Database
Characters
+
Application
Metadata
◼ Indexes: to represent relationships among the data
and also to improve the performance of DB appls
◼ Application metadata: The structure of a data entry
form, or a report
26
DBMS
◼ A toolkit which helps system developers to
design and implement the system; and users
to employ it
◼ A s/w used by people/programs to interface
with the DB
◼ Some DBMS programs are used:
– To define and build both the DB and DB
applications
– To process data in the DB
– To provide administrative facilities
27
Generic DBMS Functions
◼ Store, retrieve, and update user data
◼ Store, retrieve, and update meta data
◼ Enforce integrity rules and constraints
◼ Provide coordination and control facilities for
multiuser processing (multiple views of data)
◼ Enforce security constraints
◼ Provide facilities of backup and recovery
◼ Enable control over concurrent operation
◼ Provide wide variety of access methods
28
Simplified View of a DB System
◼ Computer based record keeping system
DBMS
Database
Application
Programs
End Users
Simplified view of a Database System
Data Hardware Software Users 29
Benefits of the Database Approach
◼ Shared data: possible to satisfy requirements of new
applications without adding new data to the DB
◼ Redundancy can be reduced
– Controlled Vs. Uncontrolled Redundancy
◼ Inconsistency can be avoided (to some extent)
– controlled redundancy: propagating updates
◼ Integrity (accuracy of data) can be maintained by
enforcing Integrity constraints
– Inconsistency leads to lack of integrity
– Centralized control of DB helps in avoiding these situations
– Remember: Even if redundancy is eliminated, the
database may still contain incorrect data 30
Benefits of the Database Approach
◼ Transaction support can be provided
◼ Security can be enforced
– By defining authorization checks to sensitive data
◼ Conflicting requirement can be balanced
– Provide an overall service that is “best for the enterprise”
◼ Standards can be enforced
– Particularly desirable
The provision of data independence
31
Drawbacks of the Database Approach
◼ Problems associated with centralization
– Drawbacks of data integration
– Concurrency problem
– Security
– Chances of DB failure
– Complexity of backup and recovery
◼ Cost: h/w + s/w + migration + operating costs
◼ Role of different professionals associated with
the design & development of DBMS
– DBA and DBD
32
Remember
If the DBMS does not ensure adequate
integrity, security, and privacy
and
If the database is not designed properly,
the database environment may result in
new problems.
33
Database Systems
◼ The big commercial database vendors:
– Oracle
– Microsoft (SQL Server)
– IBM (with DB2)
– Sybase
◼ Some free and open-source database systems:
– PostgreSQL
– MySQL
– SQLite
– CouchDB
– MongoDB
34