0:02
[Music]
0:06
thank you
0:09
[Music]
0:12
Hello friends welcome back to our
0:13
channel so in the previous session we
0:15
have discussed about the introduction to
0:18
normalization and why we are moving
0:19
towards the normalization
0:21
so normalization is mainly used to avoid
0:25
the redundancies and to overcome the
0:28
problems coming from the anomalies that
0:30
means while inserting the data updating
0:32
the data or deleting the data and as we
0:35
discussed in the previous session so
0:37
this normalization comes with the
0:38
different levels so coming from the 1nf
0:41
two NF 3 and F B C and F 4 NF and 500
0:45
these are all called as a normal forms
0:48
right so if any relation if any relation
0:51
or any database okay so which satisfies
0:54
up to the third normal form and the vcnf
0:57
that implies the database design is a
0:59
good design the schema is a good design
1:02
right so in this session
1:05
we'll start with the first level that is
1:07
a 1nf so from the unnormalized data to 1
1:11
NF how can we convert or how can we know
1:14
that whether the relation is in one and
1:17
a format so
1:19
one
1:20
NF so this is also called as
1:24
first
1:25
normal form first normal form
1:30
so the input the input
1:33
for this one is
1:35
unnormalized data
1:37
and normalize the data
1:41
and
1:42
output will be a relation
1:47
relation
1:50
with 1 and F such relation satisfies
1:54
with one angle so that will be the
1:55
output
1:57
and see how
1:59
can say the relation is in one
2:01
s right so the first point
2:05
all the attributes all the attribute
2:09
values
2:10
all the attribute values
2:13
should be atomic
2:17
should be atomic
2:19
so that means it should have a single
2:22
single value and
2:25
attributes
2:29
should not have
2:34
multi-valued attributes or multi values
2:39
or composite that means the attribute
2:43
can't be divided more right
2:53
counts
2:58
should be unique
3:00
should be unique
3:03
so
3:04
no two attributes should have a same
3:06
name
3:07
so that type of redundancy should not be
3:10
accepted in this one and F right so the
3:13
first one all the attitude value should
3:15
be Atomic and attribute should not have
3:17
any multi values or a composite so every
3:20
attribute should have only single value
3:22
and all the attributes should be unique
3:24
so they should not be
3:26
redundancy on the attributes so all the
3:29
attributes should be unique no no two
3:32
attributes should have the same name
3:34
so if if any relation satisfies these
3:37
three points we can simply call it as a
3:40
one at F so we can say the relation is
3:43
in one atom let me tell you an example
3:45
this is this is a very simple normal
3:48
form
3:49
so let us take the student details
3:54
student table with a student ID
3:58
student name and course
4:03
related to that particular student okay
4:05
enrolled by the student so let it be
4:09
some 101 is a ID
4:13
Sandeep is a student name so Sandeep
4:16
enroll to C
4:18
C plus plus
4:20
Java
4:21
so one student enrolled 2 multiple
4:25
courses multiple courses
4:29
next
4:31
coming to the second one
4:34
zero two
4:36
let us take the name of the student is
4:38
sarathi enroll to C plus plus
4:42
python
4:44
C plus percent python let us take the
4:47
third one
4:51
satwik
4:54
and roll two
4:57
Java
4:58
python
5:02
now let us check whether the this
5:05
particular table so this is a primary
5:07
primary key let us check whether this
5:10
table
5:11
satisfies the 1 and F the points we have
5:14
discussed it just now the first one so
5:16
it should be having Atomic values yes
5:19
second one it should not contain the
5:22
multiple values or a composite values so
5:25
all these two are not a composite and
5:27
this is also not a composite so
5:28
composite means further divided okay if
5:31
the attribute is furtherly divided so we
5:33
can say it as a composite and see uh
5:37
course there are multiple
5:40
values for the particular course so C C
5:43
plus plus and Java and it violates the
5:47
second point it should not contain a
5:49
multi values so we have to avoid this
5:52
one so how can we avoid this one simply
5:55
we can include another row with this
5:59
particular details
6:01
okay so that will avoid the multiple
6:03
values and all the attributes should be
6:05
unique so there are no two attributes
6:07
with the same name yes that's satisfied
6:09
so only one point that violates the one
6:12
and F is multi values so this can be
6:17
converted to
6:19
yes ID
6:21
yes name
6:23
and of course
6:25
and you can see 1 0 1
6:28
Sandeep enrolled to c one zero one
6:34
Sunday
6:35
enroll to C plus plus one zero one
6:39
Sunday
6:41
enroll to
6:43
Java similarly one zero two
6:47
Saturday
6:49
enroll to C plus plus
6:52
one zero three sarathi
6:56
and roll two
6:58
python
7:00
and one zero sorry one zero two itself
7:02
right next one zero three
7:06
satwik
7:08
enroll two
7:11
Java
7:12
one zero three
7:14
satwik
7:17
and roll two
7:21
python so
7:24
you can observe this is the table
7:31
which satisfies all the points which we
7:34
have discussion for 1 and F
7:45
so this is a
7:47
table now you can see
7:50
we have converted this type of relation
7:53
to this relation now you can see there
7:56
are no multi values multi-valued
7:59
attributes right so num of the attribute
8:02
is having a multiple values so in order
8:04
to avoid that if we are having this one
8:06
in order to avoid that just inside one
8:08
more row okay insert one more row so
8:10
like this we can avoid the multi values
8:13
so every attribute is having only one
8:16
value every cell is having only one
8:18
value
8:19
right so this if the relation is in this
8:23
form we can say this is in 1 and f that
8:28
is the first normal form okay this is
8:30
unnormalized
8:35
a relation unnormalized relation so this
8:39
is the relation with 1 and F relation in
8:42
one and F so from here we need to go
8:46
with the next levels so coming to the
8:48
2nf if you want to find out whether this
8:51
relation is in 2nf so first it should
8:53
satisfy the one and F conditions that
8:56
means the input for two NF is the
8:59
relation with 1 and F
9:01
okay the input for 2nf will be relation
9:04
with 1 and F so input for this 1nf is on
9:07
normalized data so from that we have to
9:10
achieve the 100. right so hope you're
9:13
understood this first normal form so
9:15
let's stop here in the next session
9:17
we'll go with the another level that is
9:19
a two Ender right so if you are having
9:21
any doubts regarding this one feel free
9:23
to post your notes in the comment
9:24
section definitely I will try to clarify
9:26
all your doubts and if you really
9:27
enjoyed my session like my session share
9:30
my session with your friends and don't
9:31
forget to subscribe to our Channel
9:33
thanks for watching thank you very much