Normalization is a technique for organizing data in relational database tables to reduce redundancy and improve data integrity. It involves decomposing tables to eliminate anomalies and inconsistencies. The goals of normalization are to minimize duplicate data, ensure data dependencies make logical sense, and simplify table designs to make them easier to maintain over time. There are several forms of normalization with the main ones being first, second, third normal form. The advantages include a more efficient database structure, avoidance of data anomalies, and easier maintenance of data. Some disadvantages are reduced performance due to additional joins required between tables and increased complexity of data changes.

1. What is
Normalization?
WELCOME TO DUCAT INDIA
Language | Industrial Training | Digital Marketing | Web Technology | Testing+ | Database | Networking |
Mobile Application | ERP | Graphic | Big Data | Cloud Computing
7070905090
info@ducatindia.co

2. What is Normalization?
Normalization is the technique of decomposing relational tables with
anomalies to generate smaller and well-organized relations. The fundamental
aim of normalization is to reduce redundancy, which represents that data to
be saved only once in a relation. Normalization was established by IBM
researcher E.F. Codd in the 1970s.
Reasons for Normalization
There are four reasons for normalization are as follows.
1.To structure the data so that any pertinent relationship between entities can be
represented.
2.To allow easy retrieval of data in response to query report requests.
3.To facilitate the maintenance of the data through updation, insertions, and deletions.
4.To reduce the need to reconstruct or reorganize information when new application
requirements arise.

3. Advantages of Normalization
1.It is a more productive data mechanism.
2.To avoid redundant fields or columns.
3.It is a more flexible data structure, i.e., and we should be able to insert new rows and
data values simply.
4.It is easier to maintain the data structure, i.e., it is easy to perform operations, and
complex queries can be easily managed.
5.To minimizes data duplication.
6.Free from modification anomalies.

4. Disadvantages of Normalization
Performance
In a normalized database, extra joins are needed to recover information from numerous tables. Joins
need additional I/O and may raise the system overhead than single-table lookups. In addition, more
often, a normalized database acquires an extra CPU processor to carry out join logic and to keep up
with data and referential integrity.
Normalization Procedures
Proper normalization of the database is very important. There is no tested tool for detailed
normalization. Most normalization is done manually. There is a chance of an improperly normalized
database, which can cause significant problems.

5. Database Restructuring
Proper database design is also important because it can be very difficult to modify the
structure of a database after the fact. Database restructuring cannot be easy as the
database generally serves as the back-end of a larger application. Changes to the
database may scrap the application.
Data Insertion and Maintenance
Though a fully normalized database makes it easy to retrieve data, sometimes insertion and
updating rows can be problematic. It is very difficult when they have referential integrity on
themselves. The object-oriented database management system (OODBMS) can solve these
problems largely. Many of the complex Web applications, particularly banking and high-volume
community sites, would be better served by using an OODBMS.
(Read More on https://tutorials.ducatindia.com/dbms/what-is-normalization/)

6. THANK YOU
7070905090
info@ducatindia.co
m