What is Database

The database is a collection of inter-related data which is used to retrieve, insert

and delete the data efficiently. It is also used to organize the data in the form of a
table, schema, views, and reports, etc.

The college Database organizes the data about the admin, staff, students and
faculty etc.
Using the database, you can easily retrieve, insert, and delete the information.

• Database management system is a software which is used to manage the

database. For example: MySQL, Oracle, etc are a very popular commercial
database which is used in different applications.
• DBMS provides an interface to perform various operations like database
creation, storing data in it, updating data, creating a table in the database
and a lot more.
• It provides protection and security to the database. In the case of multiple
users, it also maintains data consistency.

Advantages of DBMS
• Controls database redundancy: It can control data redundancy because
it stores all the data in one single database file and that recorded data is
placed in the database.
• Data sharing: In DBMS, the authorized users of an organization can share
the data among multiple users.
• Easily Maintenance: It can be easily maintainable due to the centralized
nature of the database system.
• Reduce time: It reduces development time and maintenance need.
• Backup: It provides backup and recovery subsystems which create
automatic backup of data from hardware and software failures and
restores the data if required.
• multiple user interface: It provides different types of user interfaces like
graphical user interfaces, application program interfaces
 Disadvantages of DBMS
• Cost of Hardware and Software: It requires a high speed of data
processor and large memory size to run DBMS software.
• Size: It occupies a large space of disks and large memory to run them
efficiently.
• Complexity: Database system creates additional complexity and
requirements.
• Higher impact of failure: Failure is highly impacted the database
because in most of the organization, all the data stored in a single
database and if the database is damaged due to electric failure or
database corruption then the data may be lost forever

DBMS(Database Management System)

Database Management System is basically software that manages
the collection of related data. It is used for storing data and
retrieving the data effectively when it is needed. It also provides
proper security measures for protecting the data from
unauthorized access. In Database Management System the data
can be fetched by SQL queries and relational algebra. It also
provides mechanisms for data recovery and data backup.
0 seconds of 14 secondsVolume 0%

Example:
Oracle, MySQL, MS SQL server.

Difference between File System and DBMS

Basics File System DBMS

Structure The file system is a way of DBMS is software for

arranging the files in a storage managing the database.
medium within a computer.

Data Redundant data can be present In DBMS there is no

Redundancy in a file system. redundant data.
Backup and It doesn’t provide Inbuilt It provides in house tools
Recovery mechanism for backup and for backup and recovery of
recovery of data if it is lost. data even if it is lost.

Query There is no efficient query Efficient query processing is

processing processing in the file system. there in DBMS.

Consistency There is less data consistency in There is more data

the file system. consistency because of the
process of normalization.

Complexity It is less complex as compared It has more complexity in

to DBMS. handling as compared to
the file system.

Security File systems provide less DBMS has more security

Constraints security in comparison to DBMS. mechanisms as compared
to file systems.

Cost It is less expensive than DBMS. It has a comparatively

higher cost than a file
system.

Data There is no data independence. In DBMS data

Independence independence exists, mainly
of two types:
1) Logical Data
Independence.
2)Physical Data
Independence.

User Access Only one user can access data Multiple users can access
at a time. data at a time.

Meaning The users are not required to The user has to write
write procedures. procedures for managing
databases
Sharing Data is distributed in many files. Due to centralized nature
So, it is not easy to share data. data sharing is easy

Data It give details of storage and It hides the internal details

Abstraction representation of data of Database

Integrity Integrity Constraints are difficult Integrity constraints are

Constraints to implement easy to implement

Attributes To access data in a file , user No such attributes are

requires attributes such as file required.
name, file location.

Example Cobol, C++ Oracle, SQL Server

DBMS 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.
• The client/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.
 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.
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.
Structure of dbms
Introduction of ER Model

The Entity Relational Model is a model for identifying entities to be represented in the database
and representation of how those entities are related. The ER data model specifies enterprise
schema that represents the overall logical structure of a database graphically.

The Entity Relationship Diagram explains the relationship among the entities present in the
database. ER models are used to model real-world objects like a person, a car, or a company
and the relation between these real-world objects. In short, the ER Diagram is the structural
format of the database.

Why Use ER Diagrams In DBMS?

ER diagrams are used to represent the E-R model in a database, which makes them easy to
convert into relations (tables).

ER diagrams provide the purpose of real-world modeling of objects which makes them intently
useful.

ER diagrams require no technical knowledge and no hardware support.

These diagrams are very easy to understand and easy to create even for a naive user.

It gives a standard solution for visualizing the data logically.

Symbols Used in ER Model

ER Model is used to model the logical view of the system from a data perspective which
consists of these symbols:

Rectangles: Rectangles represent Entities in the ER Model.

Ellipses: Ellipses represent Attributes in the ER Model.

Diamond: Diamonds represent Relationships among Entities.

Lines: Lines represent attributes to entities and entity sets with other relationship types.

Double Ellipse: Double Ellipses represent Multi-Valued Attributes.

Double Rectangle: Double Rectangle represents a Weak Entity.

Symbols used in ER Diagram

Symbols used in ER Diagram

Entity
An Entity may be an object with a physical existence – a particular person,
car, house, or employee – or it may be an object with a conceptual existence
– a company, a job, or a university course.
Entity Set: An Entity is an object of Entity Type and a set of all entities is
called an entity set. For Example, E1 is an entity having Entity Type Student
and the set of all students is called Entity Set. In ER diagram, Entity Type is
represented as:
1. Strong Entity

A Strong Entity is a type of entity that has a key Attribute. Strong Entity does not depend on other
Entity in the Schema. It has a primary key, that helps in identifying it uniquely, and it is
represented by a rectangle. These are called Strong Entity Types.

2. Weak Entity

An Entity type has a key attribute that uniquely identifies each entity in the entity set. But some
entity type exists for which key attributes can’t be defined. These are called Weak Entity types.

For Example, A company may store the information of dependents (Parents, Children, Spouse)
of an Employee. But the dependents don’t have existed without the employee. So Dependent
will be a Weak Entity Type and Employee will be Identifying Entity type for Dependent, which
means it is Strong Entity Type.

A weak entity type is represented by a Double Rectangle. The participation of weak entity types
is always total. The relationship between the weak entity type and its identifying strong entity
type is called identifying relationship and it is represented by a double diamond.

Attributes

Attributes are the properties that define the entity type. For example, Roll_No, Name, DOB, Age,
Address, and Mobile_No are the attributes that define entity type Student. In ER diagram, the
attribute is represented by an oval.

Attribute

1. Key Attribute

The attribute which uniquely identifies each entity in the entity set is called the key attribute.
For example, Roll_No will be unique for each student. In ER diagram, the key attribute is
represented by an oval with underlying lines.

Key Attribute
2. Composite Attribute

An attribute composed of many other attributes is called a composite attribute. For example,
the Address attribute of the student Entity type consists of Street, City, State, and Country. In ER
diagram, the composite attribute is represented by an oval comprising of ovals.

Composite Attribute

3. Multivalued Attribute

An attribute consisting of more than one value for a given entity. For example, Phone_No (can be
more than one for a given student). In ER diagram, a multivalued attribute is represented by a
double oval.

Multivalued Attribute

4. Derived Attribute

An attribute that can be derived from other attributes of the entity type is known as a derived
attribute. e.g.; Age (can be derived from DOB). In ER diagram, the derived attribute is
represented by a dashed oval.

Derived Attribute

The Complete Entity Type Student with its Attributes can be represented as:
Entity and Attributes

Relationship Type and Relationship Set

A Relationship Type represents the association between entity types. For example, ‘Enrolled in’
is a relationship type that exists between entity type Student and Course. In ER diagram, the
relationship type is represented by a diamond and connecting the entities with lines.

Entity-Relationship Set

A set of relationships of the same type is known as a relationship set. The following relationship
set depicts S1 as enrolled in C2, S2 as enrolled in C1, and S3 as registered in C3.
Relationship Set

Degree of a Relationship Set

The number of different entity sets participating in a relationship set is called the degree of a
relationship set.

1. Unary Relationship: When there is only ONE entity set participating in a relation, the
relationship is called a unary relationship. For example, one person is married to only one
person.

Unary Relationship

2. Binary Relationship: When there are TWO entities set participating in a relationship, the
relationship is called a binary relationship. For example, a Student is enrolled in a Course.

Binary Relationship
3. n-ary Relationship: When there are n entities set participating in a relation, the relationship
is called an n-ary relationship.

Cardinality

The number of times an entity of an entity set participates in a relationship set is known
as cardinality. Cardinality can be of different types:

1. One-to-One: When each entity in each entity set can take part only once in the relationship,
the cardinality is one-to-one. Let us assume that a male can marry one female and a female can
marry one male. So the relationship will be one-to-one.

the total number of tables that can be used in this is 2.

Using Sets, it can be represented as:

Set Representation of One-to-One

2. One-to-Many: In one-to-many mapping as well where each entity can be related to more
than one relationship and the total number of tables that can be used in this is 2. Let us assume
that one surgeon department can accommodate many doctors. So the Cardinality will be 1 to
M. It means one department has many Doctors.
total number of tables that can used is 3.

one to many cardinality

Using sets, one-to-many cardinality can be represented as:

Set Representation of One-to-Many

3. Many-to-One: When entities in one entity set can take part only once in the relationship set
and entities in other entity sets can take part more than once in the relationship set, cardinality
is many to one. Let us assume that a student can take only one course but one course can be
taken by many students. So the cardinality will be n to 1. It means that for one course there can
be n students but for one student, there will be only one course.

The total number of tables that can be used in this is 3.

many to one cardinality

Using Sets, it can be represented as:

Set Representation of Many-to-One

In this case, each student is taking only 1 course but 1 course has been taken by many
students.

4. Many-to-Many: When entities in all entity sets can take part more than once in the
relationship cardinality is many to many. Let us assume that a student can take more than one
course and one course can be taken by many students. So the relationship will be many to
many.

the total number of tables that can be used in this is 3.

many to many cardinality

Using Sets, it can be represented as:

Many-to-Many Set Representation

In this example, student S1 is enrolled in C1 and C3 and Course C3 is enrolled by S1, S3, and
S4. So it is many-to-many relationships.
Participation Constraint

Participation Constraint is applied to the entity participating in the relationship set.

1. Total Participation – Each entity in the entity set must participate in the relationship. If each
student must enroll in a course, the participation of students will be total. Total participation is
shown by a double line in the ER diagram.

2. Partial Participation – The entity in the entity set may or may NOT participate in the
relationship. If some courses are not enrolled by any of the students, the participation in the
course will be partial.

The diagram depicts the ‘Enrolled in’ relationship set with Student Entity set having total
participation and Course Entity set having partial participation.

Total Participation and Partial Participation

Using Set, it can be represented as,

Set representation of Total Participation and Partial Participation

Every student in the Student Entity set participates in a relationship but there exists a course C4
that is not taking part in the relationship.

How to Draw ER Diagram?

• The very first step is Identifying all the Entities, and place them in a Rectangle, and
labeling them accordingly.

• The next step is to identify the relationship between them and pace them accordingly
using the Diamond, and make sure that, Relationships are not connected to each other.
• Attach attributes to the entities properly.

• Remove redundant entities and relationships.

• Add proper colors to highlight the data present in the database.