Difference Between File System and DBMS

Basics File System DBMS

The file system is a way of

DBMS is software for managing
arranging the files in a storage
the database.
Structure medium within a computer.

Data Redundant data can be present In DBMS there is no redundant

Redundancy in a file system. data.

It doesn’t provide Inbuilt It provides in house tools for

Backup and mechanism for backup and backup and recovery of data even
Recovery recovery of data if it is lost. if it is lost.

Query There is no efficient query Efficient query processing is there

processing processing in the file system. in DBMS.

There is more data consistency

There is less data consistency
because of the process
in the file system.
Consistency of normalization .

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

Complexity to DBMS. as compared to the file system.

File systems provide less DBMS has more security

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

It has a comparatively higher cost

It is less expensive than DBMS.
Cost than a file system.

In DBMS data
independence exists, mainly of
two types:
There is no data independence.
1) Logical Data Independence .
Data
kIndependence 2)Physical Data Independence.
Basics File System DBMS

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

The users are not required to The user has to write procedures
Meaning write procedures. for managing databases

Data is distributed in many files. Due to centralized nature data

Sharing So, it is not easy to share data. sharing is easy

It give details of storage and It hides the internal details

Data Abstraction representation of data of Database

Integrity Integrity Constraints are difficult Integrity constraints are easy to

Constraints to implement implement

To access data in a file , user

requires attributes such as file No such attributes are required.
Attribute s name, file location.

Example Cobol , C++ Oracle , SQL Server

3. The 3-tier architecture is a commonly used architectural approach in Database

Management Systems (DBMSs) for the design and development of applications that work
with databases. The 3-tier architecture divides an application’s components into three tiers
or layers. Each layer has its own set of responsibilities.
DBMS 3-Tier architecture divides the complete system into three inter-related but
independent modules as shown below:
DBMS 3-tier architecture
 Physical Level: At the physical level, the information about the location of database
objects in the data store is kept. Various users of DBMS are unaware of the locations
of these [Link] simple terms,physical level of a database describes how the data
is being stored in secondary storage devices like disks and tapes and also gives
insights on additional storage details.
 Conceptual Level: At conceptual level, data is represented in the form of various
database tables. For Example, STUDENT database may contain STUDENT and
COURSE tables which will be visible to users but users are unaware of their
[Link] referred as logical schema,it describes what kind of data is to be stored
in the database.
 External Level: An external level specifies a view of the data in terms of conceptual
level tables. Each external level view is used to cater to the needs of a particular
category of users. For Example, FACULTY of a university is interested in looking
course details of students, STUDENTS are interested in looking at all details related
to academics, accounts, courses and hostel details as well. So, different views can
be generated for different users. The main focus of external level is data abstraction.
 3 Tier Schema Architecture in DBMS
 In DBMS, the 3-tier architecture is a client-server architecture that separates the user
interface, application processing, and data management into three distinct tiers or
layers. The 3-tier architecture is widely used in modern web applications and
enterprise systems because it offers scalability, flexibility, and security. Here is a brief
description of each tier in the 3-tier architecture:
 Presentation Tier: The presentation tier is the user interface or client layer of the
application. It is responsible for presenting data to the user and receiving input from
the user. This tier can be a web browser, mobile app, or desktop application.
 Application Tier: The application tier is the middle layer of the 3-tier architecture. It
is responsible for processing and managing the business logic of the application.
This tier communicates with the presentation tier to receive user input and
 communicates with the data management tier to retrieve or store data. This tier may
include application servers, web servers, or APIs.
 Data Management Tier: The data management tier is the bottom layer of the 3-tier
architecture. It is responsible for managing and storing data. This tier can include
databases, data warehouses, or data lakes. The data management tier
communicates with the application tier to receive or store data.

 3rd tier Architecture

 Benefits of 3-Tier Architecture
 The 3-tier architecture in DBMS provides several benefits, including:
 Scalability: The architecture separates the application processing and data
management layers, which allows for easy scalability of each layer independently.
 Flexibility: The architecture allows for the replacement or upgrade of one layer
without affecting the other layers.
 Security: The architecture provides an additional layer of security, as the data
management tier can be isolated from the application and presentation tiers,
reducing the risk of unauthorized access.
 Overall, the 3-tier architecture in DBMS is a flexible, scalable, and secure approach
to building modern web applications and enterprise systems. It separates the user
interface, application processing, and data management into distinct layers, providing
clear boundaries between each layer and improving system performance, reliability,
and maintainability.
Components of DBMS
There are many components available in the DBMS. Each component has a
significant task in the DBMS. A database environment is a collection of components
that regulates the use of data, management, and a group of data. These components
consist of people, the technique of Handel the database, data, hardware, software,
 etc. there are several components available for the DBMS. We are going to explain
five main topics of the database below.

1. Hardware
o Here the hardware means the physical part of the DBMS. Here the hardware
includes output devices like a printer, monitor, etc., and storage devices like a hard
disk.
o In DBMS, information hardware is the most important visible part. The equipment
which is used for the visibility of the data is the printer, computer, scanner, etc. This
equipment is used to capture the data and present the output to the user.
o With the help of hardware, the DBMS can access and update the database.

o The server can store a large amount of data, which can be shared with the help of
the user's own system.
o The database can be run in any system that ranges from microcomputers to
mainframe computers. And this database also provides an interface between the real
worlds to the database.
o When we try to run any database software like MySQL, we can type any commands
with the help of our keyboards, and RAM, ROM, and processor are part of our
computer system.
 2. Software
o Software is the main component of the DBMS.

o Software is defined as the collection of programs that are used to instruct the
computer about its work. The software consists of a set of procedures, programs,
and routines associated with the computer system's operation and performance.
Also, we can say that computer software is a set of instructions that is used to
instruct the computer hardware for the operation of the computers.
o The software includes so many software like network software and operating
software. The database software is used to access the database, and the database
application performs the task.
o This software has the ability to understand the database accessing language and
then convert these languages to real database commands and then execute the
database.
o This is the main component as the total database operation works on a software or
application. We can also be called as database software the wrapper of the whole
physical database, which provides an easy interface for the user to store, update and
delete the data from the database.
o Some examples of DBMS software include MySQL, Oracle, SQL Server, dBase,
FileMaker, Clipper, Foxpro, Microsoft Access, etc.
3. Data
o The term data means the collection of any raw fact stored in the database. Here the
data are any type of raw material from which meaningful information is generated.
o The database can store any form of data, such as structural data, non-structural
data, and logical data.
o The structured data are highly specific in the database and have a structured format.
But in the case of non-structural data, it is a collection of different types of data, and
these data are stored in their native format.
o We also call the database the structure of the DBMS. With the help of the database,
we can create and construct the DBMS. After the creation of the database, we can
create, access, and update that database.
o The main reason behind discovering the database is to create and manage the data
within the database.
o Data is the most important part of the DBMS. Here the database contains the actual
data and metadata. Here metadata means data about data.
o For example, when the user stores the data in a database, some data, such as the
size of the data, the name of the data, and some data related to the user, are stored
within the database. These data are called metadata.
4. Procedures
o The procedure is a type of general instruction or guidelines for the use of DBMS. This
instruction includes how to set up the database, how to install the database, how to
 log in and log out of the database, how to manage the database, how to take a
backup of the database, and how to generate the report of the database.
o In DBMS, with the help of procedure, we can validate the data, control the access
and reduce the traffic between the server and the clients. The DBMS can offer better
performance to extensive or complex business logic when the user follows all the
procedures correctly.
o The main purpose of the procedure is to guide the user during the management and
operation of the database.
o The procedure of the databases is so similar to the function of the database. The
major difference between the database procedure and database function is that the
database function acts the same as the SQL statement. In contrast, the database
procedure is invoked using the CALL statement of the DBMS.
o Database procedures can be created in two ways in enterprise architecture. These
two ways are as below.
o The individual object or the default object.

o The operations in a container.

1. CREATE [OR REPLACE] PROCEDURE procedure_name (<Argument> {IN, OUT, IN

OUT}
2. <Datatype>,...)
3. IS
4. Declaration section<variable, constant> ;
5. BEGIN
6. Execution section
7. EXCEPTION
8. Exception section
9. END
5. Database Access Language
o Database Access Language is a simple language that allows users to write
commands to perform the desired operations on the data that is stored in the
database.
o Database Access Language is a language used to write commands to access,
upsert, and delete data stored in a database.
o Users can write commands or query the database using Database Access Language
before submitting them to the database for execution.
o Through utilizing the language, users can create new databases and tables, insert
data and delete data.
o Examples of database languages are SQL (structured query language), My Access,
Oracle, etc. A database language is comprised of two languages.
 1. Data Definition Language(DDL):It is used to construct a database. DDL
implements database schema at the physical, logical, and external levels.
Advertisement
The following commands serve as the base for all DDL commands:
o ALTER<object>

o COMMENT

o CREATE<object>

o DESCRIBE<object>

o DROP<object>

o SHOW<object>

o USE<object>

2. Data Manipulation Language(DML): It is used to access a database. The DML

provides the statements to retrieve, modify, insert and delete the data from the
database.
The following commands serve as the base for all DML commands:
o INSERT

o UPDATE

o DELETE

o LOCK

o CALL

o EXPLAIN PLAN

6. People
o The people who control and manage the databases and perform different types of
operations on the database in the DBMS.
o The people include database administrator, software developer, and End-user.

o Database administrator-database administrator is the one who manages the

complete database management system. DBA takes care of the security of the
DBMS, its availability, managing the license keys, managing user accounts and
access, etc.
o Software developer- theThis user group is involved in developing and designing the
parts of DBMS. They can handle massive quantities of data, modify and edit
databases, design and develop new databases, and troubleshoot database issues.
o End user - These days, all modern web or mobile applications store user data. How
do you think they do it? Yes, applications are programmed in such a way that they
collect user data and store the data on a DBMS system running on their server. End
users are the ones who store, retrieve, update and delete data.
o The users of the database can be classified into different groups.

o Native Users

o Online Users

o Sophisticated Users

o Specialized Users

o Application Users

o DBA - Database Administrator

Domain Application

E-commerce websites like Amazon, Flipkart, etc., have a DBMS

E-commerce of their customers. They have a track of orders sold, orders
returned, defective pieces, etc.

Schools have databases of their students. With the rise of

Education online classes, physical attendance registers are being
replaced by DBMS.

The Train Ticket Reservation System is one of the important

examples. It has a database of lakhs and crores of customers.
Reservation
The information status can also be indicated as Waiting,
Systems
confirmed, or RAC. Not to forget to mention that the waiting
status also gets updated because of DBMS!

Manufacturing DBMS is used to keep records of all the details about the
 products like quantity, bills, purchase, supply chain
Industry
management, etc.

Data Models in DBMS



A Data Model in Database Management System (DBMS) is the concept of tools that are
developed to summarize the description of the database. Data Models provide us with a
transparent picture of data which helps us in creating an actual database. It shows us from
the design of the data to its proper implementation of data.
Types of Relational Models
1. Conceptual Data Model
2. Representational Data Model
3. Physical Data Model
It is basically classified into 3 types:-

Data Models

Aiming for a top All India Rank in GATE CS/IT or GATE DA 2026? Our courses, led by
experts like Khaleel Sir, Chandan Jha Sir, and Vijay Agarwal Sir, offer live
classes, practice problems, doubt support, quizzes, and All India Mock Tests—all in one
place.
1. Conceptual Data Model
The conceptual data model describes the database at a very high level and is useful to
understand the needs or requirements of the database. It is this model, that is used in the
requirement-gathering process i.e. before the Database Designers start making a particular
database. One such popular model is the entity/relationship model (ER model). The E/R
model specializes in entities, relationships, and even attributes that are used by database
designers. In terms of this concept, a discussion can be made even with non-computer
science(non-technical) users and stakeholders, and their requirements can be understood.
Entity-Relationship Model( ER Model): It is a high-level data model which is used to define
the data and the relationships between them. It is basically a conceptual design of any
database which is easy to design the view of data.
Components of ER Model:
1. Entity: An entity is referred to as a real-world object. It can be a name, place, object,
class, etc. These are represented by a rectangle in an ER Diagram.
2. Attributes: An attribute can be defined as the description of the entity. These are
represented by Ellipse in an ER Diagram. It can be Age, Roll Number, or Marks for a
Student.
3. Relationship: Relationships are used to define relations among different entities.
Diamonds and Rhombus are used to show Relationships.
Characteristics of a conceptual data model
 Offers Organization-wide coverage of the business concepts.
 This type of Data Models are designed and developed for a business audience.
 The conceptual model is developed independently of hardware specifications like
data storage capacity, location or software specifications like DBMS vendor and
technology. The focus is to represent data as a user will see it in the “real world.”
Conceptual data models known as Domain models create a common vocabulary for all
stakeholders by establishing basic concepts and scope
2. Representational Data Model
This type of data model is used to represent only the logical part of the database and does
not represent the physical structure of the database. The representational data model allows
us to focus primarily, on the design part of the database. A popular representational model is
a Relational model. The relational Model consists of Relational Algebra and Relational
Calculus. In the Relational Model, we basically use tables to represent our data and the
relationships between them. It is a theoretical concept whose practical implementation is
done in Physical Data Model.
The advantage of using a Representational data model is to provide a foundation to form the
base for the Physical model.
Characteristics of Representational Data Model
 Represents the logical structure of the database.
 Relational models like Relational Algebra and Relational Calculus are commonly
used.
 Uses tables to represent data and relationships.
 Provides a foundation for building the physical data model.
3. Physical Data Model
 The physical Data Model is used to practically implement Relational Data Model. Ultimately,
all data in a database is stored physically on a secondary storage device such as discs and
tapes. This is stored in the form of files, records, and certain other data structures. It has all
the information on the format in which the files are present and the structure of the
databases, the presence of external data structures, and their relation to each other. Here,
we basically save tables in memory so they can be accessed efficiently. In order to come up
with a good physical model, we have to work on the relational model in a better
way. Structured Query Language (SQL) is used to practically implement Relational Algebra.
This Data Model describes HOW the system will be implemented using a specific DBMS
system. This model is typically created by DBA and developers. The purpose is actual
implementation of the database.
Characteristics of a physical data model:
 The physical data model describes data need for a single project or application
though it maybe integrated with other physical data models based on project scope.
 Data Model contains relationships between tables that which addresses cardinality
and nullability of the relationships.
 Developed for a specific version of a DBMS, location, data storage or technology to
be used in the project.
 Columns should have exact datatypes, lengths assigned and default values.
 Primary and Foreign keys, views, indexes, access profiles, and authorizations, etc.
are defined
Some Other Data Models
1. Hierarchical Model
The hierarchical Model is one of the oldest models in the data model which was developed
by IBM, in the 1950s. In a hierarchical model, data are viewed as a collection of tables, or we
can say segments that form a hierarchical relation. In this, the data is organized into a tree-
like structure where each record consists of one parent record and many children. Even if
the segments are connected as a chain-like structure by logical associations, then the
instant structure can be a fan structure with multiple branches. We call the illogical
associations as directional associations.
2. Network Model
The Network Model was formalized by the Database Task group in the 1960s. This model is
the generalization of the hierarchical model. This model can consist of multiple parent
segments and these segments are grouped as levels but there exists a logical association
between the segments belonging to any level. Mostly, there exists a many-to-many logical
association between any of the two segments.
3. Object-Oriented Data Model
In the Object-Oriented Data Model, data and their relationships are contained in a single
structure which is referred to as an object in this data model. In this, real-world problems are
represented as objects with different attributes. All objects have multiple relationships
between them. Basically, it is a combination of Object Oriented programming and a
Relational Database Model.
4. Float Data Model
The float data model basically consists of a two-dimensional array of data models that do not
contain any duplicate elements in the array. This data model has one drawback it cannot
store a large amount of data that is the tables can not be of large size.
5. Context Data Model
The Context data model is simply a data model which consists of more than one data model.
For example, the Context data model consists of ER Model, Object-Oriented Data Model,
etc. This model allows users to do more than one thing which each individual data model
can do.
6. Semi-Structured Data Model
Semi-Structured data models deal with the data in a flexible way. Some entities may have
extra attributes and some entities may have some missing attributes. Basically, you can
represent data here in a flexible way.
Advantages of Data Models
1. Data Models help us in representing data accurately.
2. It helps us in finding the missing data and also in minimizing Data Redundancy.
3. Data Model provides data security in a better way.
4. The data model should be detailed enough to be used for building the physical
database.
5. The information in the data model can be used for defining the relationship between
tables, primary and foreign keys, and stored procedures.
Disadvantages of Data Models
1. In the case of a vast database, sometimes it becomes difficult to understand the data
model.
2. You must have the proper knowledge of SQL to use physical models.
3. Even smaller change made in structure require modification in the entire application.
4. There is no set data manipulation language in DBMS.
5. To develop Data model one should know physical data stored characteristics.
Conclusion
In conclusion, data modeling is a crucial process for designing databases that ensure
consistency, quality, and accuracy in how data is stored and managed. It establishes a
structured framework using conceptual, logical, and physical models to define entities,
relationships, and implementation details. While data modeling supports better organization
and ensures data integrity, it can be challenging due to the impact of structural changes on
the entire application. Despite its drawbacks, data modeling is essential for creating efficient,
reliable, and scalable database systems.
Frequently Asked Questions on Data Models – FAQ’s
What do you mean by data model?
A data model is a conceptual framework used to define and organize the structure,
relationships, and rules of data in a database. It specifies how data is stored, connected, and
manipulated. A data model provides a blueprint for designing and managing databases,
ensuring consistency and clarity in data organization. Common types of data models include
hierarchical, network, relational, and object-oriented models.
What are the 3 components of a data model?
The three main components of a data model are:
1. Structural Component:
Defines how data is organized and structured in the database, such as tables, rows,
columns (in a relational model), or nodes and edges (in a graph model).
2. Behavioral Component:
Describes how data can be accessed and manipulated, including operations like
retrieval, insertion, updating, and deletion (e.g., SQL queries in a relational model).
3. Constraint Component:
Specifies rules and restrictions to ensure data integrity and consistency, such as
primary keys, foreign keys, and unique constraints.
What is a Hierarchical Data Model?
The hierarchical data model is the oldest type of the data model. It was developed by
IBM in 1968. It organizes data in a tree-like structure. Hierarchical model consists of the
following :
 It contains nodes which are connected by branches.
 The topmost node is called the root node.
 If there are multiple nodes appear at the top level, then these can be called root
segments.
 Each node has exactly one parent.
 One parent may have many children.
Aiming for a top All India Rank in GATE CS/IT or GATE DA 2026? Our courses, led by
experts like Khaleel Sir, Chandan Jha Sir, and Vijay Agarwal Sir, offer live
classes, practice problems, doubt support, quizzes, and All India Mock Tests—all in
one place.
In the above figure, Electronics is the root node which has two children i.e. Televisions
and Portable Electronics. These two has further children for which they act as parent.
For example: Television has children as Tube, LCD and Plasma, for these three
Television act as parent. It follows one to many relationship.
Advantages of the Hierarchical Data Model
 Because of its tree form, it is easy to grasp.
 Retrieving data in a one-to-many connection is efficient.
Disadvantages of the Hierarchical Data Model
 Inflexibility in reorganizing data.
 accessing complicated data structures may be challenging.
 redundant data storage, which might cause anomalies and inconsistencies.
What is a Network Data Model?
It is the advance version of the hierarchical data model. To organize data it uses directed
graphs instead of the tree-structure. In this child can have more than one parent. It uses
the concept of the two data structures i.e. Records and Sets.

In the above figure, Project is the root node which has two children i.e. Project 1 and
Project 2. Project 1 has 3 children and Project 2 has 2 children. Total there are 5 children
i.e Department A, Department B and Department C, they are network related children as
we said that this model can have more than one parent. So, for the Department B and
Department C have two parents i.e. Project 1 and Project 2.
Advantages of the Network Data Model
 Because of its numerous parent ties, it is more adaptable than the hierarchical
approach.
 Ideal for managing intricate, many-to-many connections.
Disadvantages of the Network Data Model
 Increased complexity in database design and management.
 requires complex programming in order to manage and work with data.
What is a Relational Data Model?
The relational data model was developed by E.F. Codd in 1970. There are no physical
links as they are in the hierarchical data model. Following are the properties of the
relational data model :
 Data is represented in the form of table only.
 It deals only with the data not with the physical structure.
 It provides information regarding metadata.
 At the intersection of row and column there will be only one value for the tuple.
 It provides a way to handle the queries with ease.

Advantages of the Relational Data Model

 High data independence and flexibility.
 offers robust and user-friendly querying features.
 removes duplication by use of normalization.
Disadvantages of the Relational Data Model
 For certain kinds of straightforward data retrieval tasks, they may not perform as well
as hierarchical models.
 demands a deeper comprehension of SQL and normalization principles.
Difference Between Hierarchical, Network and Relational Data Model
Hierarchical Data Relational Data
Model Network Data Model Model

In this model, to store It organizes records in

data hierarchy method It organizes records to the form of table and
is used. It is the oldest one another through links relationship between
method and not in use or pointers. tables are set using
today. common fields.

To organize records, it It organizes records in the It organizes records in

uses tree structure. form of directed graphs. the form of tables.

In addition to 1:1 and

In addition to 1:1 and 1:n
It implements 1:1 and 1:n it also implements
it also implements many
1:n relations. many to many
to many relationships.
relationships.

The logical
Pointers are used to
A linked list is used to representation is used
establish relationships
establish a relationship with rows and columns
among records
among records physically. to depict relationship
physically.
among records.

Insertion
anomaly exits in this
model i.e. child node There is no insertion There is no insertion
cannot be inserted anomaly. anomaly.
without the parent
node.

Deletion anomaly
exists in this model i.e. There is no deletion There is no deletion
it is difficult to delete anomaly. anomaly.
the parent node.

Update leads to Updating a record is

inconsistency easy and simple with
No such problem as only
problems because of the process of
one instance of records
the existence of normalization, the
exist.
multiple instances of a redundant data gets
child record. removed.
Hierarchical Data Relational Data
Model Network Data Model Model

There is partial data

This model lacks data This model provides
independence in this
independence. data independence.
model.

No such facility for No such facility for

SQL-based declarative
querying database is querying database is
querying is supported.
supported. supported.

It is used to access
It is used to access the It is used to access the
the data which is
data which is complex data which is complex
complex and
and symmetric. and symmetric.
asymmetric.

Difficult to design a
It is easy to
database and manipulate
Difficult to design a comprehend due to
a database because of its
database because of concealed physical
complexity. Hence, it
its complexity. level details from end-
imposes a burden on the
users.
programmer.

It is flexible as
It is flexible as compared
It is less flexible. compared to the
to the hierarchical model.
hierarchical model.

VAX-DBMS, DMS-1100 of
It is mostly used in real
&XML and XAML use UNIVAC and
world applications.
this model. SUPRADBMS’s use this
Oracle, SQL.
model.

Conclusion
Depending on the particular demands of the application, such as data complexity,
connections, and querying requirements, one may choose between hierarchical,
network, and relational data models. Network models, which have many parent
connections, provide more versatility than hierarchical models, which are restricted to
basic tree structures. Relational models are most often used in real-world applications
because they provide the most flexibility and querying capabilities.
Types of Normal Forms:
Normalization works through a series of stages called Normal forms. The normal forms
apply to individual relations. The relation is said to be in particular normal form if it
satisfies constraints.
Following are the various types of Normal forms:

Normal Form Description

A relation is in 1NF if it contains an

1NF
atomic value.

A relation will be in 2NF if it is in 1NF

and all non-key attributes are fully
2NF
functional dependent on the primary
key.

A relation will be in 3NF if it is in 2NF

3NF
and no transition dependency exists.

A stronger definition of 3NF is known

BCNF
as Boyce Codd's normal form.

A relation will be in 4NF if it is in

4NF Boyce Codd's normal form and has no
multi-valued dependency.

A relation is in 5NF. If it is in 4NF and

5NF does not contain any join dependency,
joining should be lossless.

Advantages of Normalization
o Normalization helps to minimize data redundancy.

o Greater overall database organization.

o Data consistency within the database.

o Much more flexible database design.

o Enforces the concept of relational integrity.

Disadvantages of Normalization
o You cannot start building the database before knowing what the user needs.

o The performance degrades when normalizing the relations to higher normal forms,
i.e., 4NF, 5NF.
o It is very time-consuming and difficult to normalize relations of a higher degree.

o Careless decomposition may lead to a bad database design, leading to serious

problems.
First Normal Form (1NF)
o A relation will be 1NF if it contains an atomic value.

o It states that an attribute of a table cannot hold multiple values. It must hold only
single-valued attribute.
o First normal form disallows the multi-valued attribute, composite attribute, and their
combinations.
Example: Relation EMPLOYEE is not in 1NF because of multi-valued attribute
EMP_PHONE.
EMPLOYEE table:

EMP_I EMP_NAM EMP_PHON EMP_STAT

D E E E

7272826385,
14 John UP
9064738238

20 Harry 8574783832 Bihar

7390372389,
12 Sam Punjab
8589830302

The above EMPLOYEE table is an unnormalized relation as it contains multiple

values corresponding to EMP_PHONE attribute i.e. these values are non-atomic. So
relations with multi value entries are called unnormalized relations.
To overcome this problem, we have to eliminate the non atomic values of
EMP_PHONE attribute.