Presentation On

Database
Management System

By
N Anusha
Venkat
 The Topics
Introduction to DBMS
Application of Database System
Data Architecture
Purpose of Database Systems
Database Users and Administrators
View of Data – Data Abstraction
Introduction to Database Design
Instances and Schemas
ER Diagrams
Data Models
Entities, Attributes and Entity Sets
Database Languages
Relationships and Relationship Sets
DDL with Commands
Additional features of ER Model
DML with Commands
Conceptual Design with ER Model
DCL with Commands
TCL with Commands
 Introduction to DBMS

• DBMS is a software or technology used to manage data from a database.

• Popular Databases are MYSQL,Oracle,MongoDB ,etc.
• DBMS is a system that enables you to store, modify and retrieve data in
an organized way.
• Theyensure data security and provide tools for managing data access
and permissions.
• They are essential for efficiently handling large volumes of information.
 Application of Database System
1. Banking: Manages customer accounts, transactions, and
financial records.
2. Airlines: Tracks flight schedules, reservations, and ticketing.
3. E-commerce: Manages product catalogs, customer orders,
and inventory.
4. Universities: Handles student records, course registrations,
and grades.
Application of Database System
Use of Database System
 Purpose of Database Systems

1. To ensure data integrity and consistency across the system.

2. To provide efficient data retrieval and manipulation capabilities.
3. To ensure data integrity and consistency across the system.
4. To allow multiple users to access and work with the data
concurrently.
 View of Data – Data Abstraction
1.Physical level: Describes how data is stored on physical
storage devices.
2.Logical level: Describes what data is stored and the
relationships between data.
3.View level: Describes how users interact with the data and
the interfaces provided.
Data abstraction simplifies interaction with the database by
hiding complex details
View of Data – Data Abstraction
 Instances and Schemas
1.Instance: The actual data stored in the database at a
specific point in time.
2.Schema: The structure of the database, defining how data is
organized.
3.Database schema: Includes tables, fields, relationships, and
constraints.

Instances can change frequently, while schemas are more

stable.
 Data Models
1.Hierarchical model: Organizes data in a tree-like structure
with parent-child relationships.
2.Network model: Uses graph structures to represent data
and relationships.
3.Relational model: Organizes data into tables with rows and
columns, using keys to define relationships.

Data models provide a framework for structuring and managing

data in databases.
1. Hierarchical Data Model
2. Network Data Model
3. Relational Data Model
 Database Languages

• Database languages can be used to read, store and update

the data in the database.
• DBMS Languages are classified into
 DDL - Used to define database structures (e.g., CREATE TABLE,
ALTER TABLE).
 DML - Used to manipulate data (e.g., SELECT, INSERT, UPDATE,
DELETE).
 Data Definition Language

• DDL stands for Data Definition Language. It is used to define database

structure.
• It is used to create schema, tables, indexes, constraints, etc. in the
database.
• Data definition language is used to store the information of metadata
like the number of tables and schemas, their names, indexes, columns
in each table, constraints, etc.
• Using the DDL statements, you can create the skeleton of the database.
 DDL Commands
• CREATE: Defines a new database object (table, index,
view, etc.).
Syntax: CREATE TABLE table_name (column1 datatype, column2
datatype, ...);
Example: CREATE TABLE students (id INT, name VARCHAR(50),
age INT);

• ALTER: Modifies an existing database object.

Syntax: ALTER TABLE table_name ADD column_name datatype;
Example: ALTER TABLE students ADD COLUMN grade
VARCHAR(2);
 DDL Commands
• DROP: Deletes an existing database object.
Syntax: DROP TABLE table_name;
Example: DROP TABLE students;

• TRUNCATE: Removes all records from a table, but not the

table itself.
Syntax: TRUNCATE TABLE table_name;
Example: TRUNCATE TABLE students;
 Data Manipulation Language
• Data Manipulation Language (DML) is a subset of SQL
responsible for managing and manipulating data within the
database.
• Common DML commands include SELECT, INSERT, UPDATE,
and DELETE.
• For example, the SELECT command retrieves data from one
or more tables, while the INSERT command adds new records
to a table.
• These commands are crucial for performing operations such
as querying, updating, and managing data within the
database.
 DML Commands
• SELECT: Retrieves data from one or more tables.
Syntax: SELECT column1, column2, ... FROM table_name;
Example: SELECT name, age FROM students;

• INSERT: Adds new records to a table.

Syntax: INSERT INTO table_name (column1, column2, ...) VALUES
(value1, value2, ...);
Example: INSERT INTO students (id, name, age) VALUES (1, 'John
Doe', 20);
 DML Commands

• UPDATE: Modifies existing records in a table.

Syntax: UPDATE table_name SET column1 = value1, column2 =
value2, ... WHERE condition;
Example: UPDATE students SET age = 21 WHERE id = 1;

• DELETE: Removes existing records from a table.

Syntax: DELETE FROM table_name WHERE condition;
Example: DELETE FROM students WHERE id = 1;
Database Architecture
 Database Architecture
• The DBMS design depends upon its architecture. The basic
client/server architecture is used to deal with a large number
of PCs, web servers, database servers and other components
that are connected with networks.
• Theclient/server architecture consists of many PCs and a
workstation which are connected via the network.
• DBMS architecture depends upon how users are connected to
the database to get their request done.
Types of DBMS Architecture
Database architecture can be seen as a single tier or multi-tier. But logically,
database architecture is of two types like: 2-tier architecture and 3-tier
architecture.

1-Tier Architecture
In this architecture, the database is directly available to the user. It means the
user can directly sit on the DBMS and uses it.
Any changes done here will directly be done on the database itself. It doesn't
provide a handy tool for end users.
The 1-Tier architecture is used for development of the local application, where
programmers can directly communicate with the database for the quick
response.
2-Tier Architecture
The 2-Tier architecture is same as basic client-server. In the two-tier
architecture, applications on the client end can directly communicate
with the database at the server side. For this interaction, API's like:
ODBC, JDBC are used.
The user interfaces and application programs are run on the client-side.
The server side is responsible to provide the functionalities like: query
processing and transaction management.
To communicate with the DBMS, client-side application establishes a
connection with the server side
3-Tier Architecture
The 3-Tier architecture contains another layer between the client and server. In
this architecture, client can't directly communicate with the server.
The application on the client-end interacts with an application server which
further communicates with the database system.
End user has no idea about the existence of the database beyond the
application server. The database also has no idea about any other user beyond
the application.
The 3-Tier architecture is used in case of large web application.
 Database Users and Administrators
1.End users: People who interact with the database through
applications.
2.Database administrators (DBAs): Manage the database
system, ensuring performance, security, and availability.
3.Application programmers: Develop applications that
interact with the database.
4.System analysts: Design the database structure and ensure
it meets business requirements.
 Introduction to Database Design
• Database design involves creating a detailed data model of
the database.
• Ensures data is organized efficiently and logically.
• Focuses on defining the data elements, structures, and
relationships.
• Helps in reducing redundancy and improving data integrity.
 ER Diagrams
ER (Entity-Relationship) diagrams: Visual representation of
the database structure.

• ER diagrams help in designing the database at a conceptual

level.
• Show entities, attributes, and relationships.
• Aid in understanding and communicating database design.
ER Diagrams
 Entities, Attributes, and Entity Sets
1.Entity: An object with a distinct existence (e.g., a person,
a book).
2.Attributes: Characteristics of an entity (e.g., name, age).
3.Entity set: A collection of similar entities (e.g., all
students).

Entities and attributes are fundamental building blocks of

database design.
Entities, Attributes, and Entity Sets
 Relationships and Relationship Sets

1.Relationship: Association between two or more entities

(e.g., a student enrolls in a course).
2.Relationship set: A collection of similar relationships (e.g.,
all enrollments).

• Relationships define how entities interact with each other.

• Help in organizing and structuring data in the database.
Relationship
Relationship Sets
 Additional Features of ER Model
Using the ER model for bigger data creates a lot of complexity while
designing a database model, So in order to minimize the complexity
Generalization, Specialization, and Aggregation were introduced in the ER
model and these were used for data abstraction in which an abstraction
mechanism is used to hide details of a set of objects. Some of the terms were
added to the Enhanced ER Model, where some new concepts were added.
These new concepts are:

• Generalization
• Specialization
• Aggregation
Generalization
Generalization is the process of extracting common properties from a set of
entities and creating a generalized entity from it. It is a bottom-up approach in
which two or more entities can be generalized to a higher-level entity if they
have some attributes in common. For Example, STUDENT and FACULTY can be
generalized to a higher-level entity called PERSON as shown in Figure 1. In this
case, common attributes like P_NAME, and P_ADD become part of a higher entity
(PERSON), and specialized attributes like S_FEE become part of a specialized
entity (STUDENT).

Generalization is also called as ‘ Bottom-up approach”.

Specialization
In specialization, an entity is divided into sub-entities based on its
characteristics. It is a top-down approach where the higher-level entity is
specialized into two or more lower-level entities. For Example, an EMPLOYEE
entity in an Employee management system can be specialized into DEVELOPER,
TESTER, etc. as shown in Figure 2. In this case, common attributes like E_NAME,
E_SAL, etc. become part of a higher entity (EMPLOYEE), and specialized
attributes like TES_TYPE become part of a specialized entity (TESTER).

Specialization is also called as ” Top-Down approch”.

Aggregation
An ER diagram is not capable of representing the relationship between an entity
and a relationship which may be required in some scenarios. In those cases, a
relationship with its corresponding entities is aggregated into a higher-level
entity. Aggregation is an abstraction through which we can represent
relationships as higher-level entity sets.

For Example, an Employee working on a project may require some machinery.

So, REQUIRE relationship is needed between the relationship WORKS_FOR and
entity MACHINERY. Using aggregation, WORKS_FOR relationship with its entities
EMPLOYEE and PROJECT is aggregated into a single entity and relationship
REQUIRE is created between the aggregated entity and MACHINERY
1. One to One Relationship
2. One to Many Relationship
3. Many to One Relationship
4. Many to Many Relationship
 Conceptual Design with ER Model
• Conceptual design focuses on creating a high-level structure of
the database.
• ER model is used to create a blueprint of the database.
• Ensures all data requirements are captured accurately.
• Provides a clear visualization of data relationships and
constraints.
THANK YOU