We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 4
NORMALIZATION VS. DENORMALIZATION APPROACH
Normalization is defined as a way of data re-organization. This helps meet two main
requirements in an enterprise data warchouse i.e. eliminating data redundancy and protecting
data dependency. On the other hand, denormalization increases the functionality of the database
system’ infrastructure. Normalized
schema design to store 8
and colt data
Products
=. —S
Categories
Data Integrity is maintained
Little to no redundant data
Many tables
Optimizes for storage of data
Data Integrity is not maintained
Redundant data is common Dene cy
reuse cee
eae
nec ae}
write ope
CNet un)
Cee moa
Nae et)
account of decomposition of
cee
PE unas)
Seaeate!
Combines data to
improve the access time
eae ee aay
Deeg tara seer
write operations is slower.
Memory consumption is
eo areas
nue!
eens Senate
number of tables are |
Perec asad
Peer) DATA WAREHOUSE VS. DATABASE
The main differences between data warehouse and database are summarized in the table below:
Database
‘A database Is an amalgamation of related data.
A database is used for recording data.
‘A database is an application-oriented collection of data,
‘A database uses Online Transactional Processing (OLTP).
Database tables and joins are normalized, therefore, more
‘complicated.
ER modeling techniques are used for designing.
Data Warehouse
Data warehouse serves as an information system that
contains historical and commutative data from one or
several sources.
‘A data warehouse is used for analyzing data.
Data warehouse is the subject-oriented collection of data.
Data warehouse uses Online Analytical Processing (OLAP).
Data warehouse tables and joins are denormalized, hence
simpler.
Data modeling techniques are used for designing.
