0:02
[Music]
0:11
hello friends welcome back to our
0:13
channel so in the previous session we'll
0:15
have seen the introduction to database
0:18
management system so in the session we
0:20
have covered what is the data and what
0:22
is the information and what is actually
0:25
the database now in today's session will
0:28
cover a more concept that is different
0:31
types of databases
0:44
right now we see different types of
0:47
databases so actually before going to
0:51
that we know that the database is a
0:53
collection of large data in a single
0:57
space now we go with the types of
1:01
databases one centralized database
1:15
centralized database here the name
1:19
itself indicates a data base is
1:21
maintained in a central level and from
1:24
that the multiple users from the
1:27
different places will be accessing the
1:30
common database that is called this
1:33
centralized database so there will be
1:35
one database and which is accessed with
1:38
the multiple users so it will be having
1:44
one database plus multiple users so many
1:54
people users will accessing the same
1:56
database that is all the centralized or
1:59
the database second one is
2:12
distributed database so here also the
2:15
name itself indicates the database is
2:17
distributed in different places so at a
2:21
time the multiple users will be
2:23
accessing the multiple database data
2:25
business so based upon the end users the
2:29
database will be divided and my at the
2:33
same time the multiple users can access
2:35
the multiple databases at the scene so
2:40
multiple databases will be there
2:42
here plus multiple users multiple users
2:57
right next the third one is the personal
3:04
database so personal database is a very
3:11
small database which is maintained by
3:13
the single user so in our personal
3:16
computers or laptops we can maintain the
3:20
database and we can access those
3:21
database right so such type of database
3:24
is maintained by the single user and use
3:27
it personally
3:28
that way we can call it as a personal
3:30
database so here the database is very
3:33
small so single user and single database
3:44
so which is used for personal purposes
3:47
okay then the fourth one is any user
3:54
database and user database so here the
4:01
end users are different users so each
4:04
user will be having their own role and
4:06
responsibilities so for that purpose
4:09
these users can access the
4:13
right so mainly these can be used in
4:18
applications different applications
4:20
right so these can be used in
4:27
applications different applications
4:30
for example if you take an office so a
4:34
managers will be accessing the database
4:36
and the users sort of programmers will
4:39
be accessing the databases right such
4:42
type of database we can call it as an
4:44
end user so he did the responsibility is
4:46
based upon the role and responsibilities
4:48
the users will be divided or categorized
4:52
right so such type of users we call it
4:56
as an end user that means who is
4:58
accessing the database whether the
5:00
programmer or the manager level so both
5:03
are having the roles and
5:04
responsibilities so both will be having
5:06
the privileges right so that is based
5:11
upon this end-user database so mainly
5:15
these will be used for applications
5:17
different applications so these are the
5:20
few types of databases next the next one
5:32
is
5:38
commercial database commercial database
5:43
so the name itself indicates commercial
5:46
means we have to pay some amount for
5:50
using those type of databases so user
5:53
how to pay the emam for accessing the
5:57
database right so that is user how to
6:06
pay for accessing the database accessing
6:14
the data from the database so the first
6:16
type of data we can call it as a
6:18
commercial database that was so purely
6:20
commercial next relational database so
6:33
which we are going to use this which we
6:37
have this is a relational database so in
6:41
the first session I have explained that
6:43
database the data will be always in
6:46
pumps of tables that is nothing but our
6:48
relational database why we call it as a
6:51
relational database because so there
6:53
will be different tables and we have to
6:55
give the relation between one table
6:57
another table so in terms of Delta is
7:03
represented in terms of tables and each
7:07
table will be containing the rows and
7:10
columns and this column we call it as
7:16
attribute and this host nothing but the
7:22
tuples we can call it as a tuple or a
7:25
record we can call it as a record all
7:29
right so collection of attributes is
7:31
nothing but a require collects of all
7:33
attributes will give a record so this
7:37
data in terms of tables is called the
7:40
relational database and here there will
7:42
be multiple tables and there will be
7:45
some relation between
7:46
and another tip so that's what we call
7:49
it as and less than Daedalus right next
7:54
cloud database cloud database so
8:03
nowadays we know that the 12 that means
8:05
large data storage so here the data will
8:09
be stored in a cloud and from the cloud
8:11
the users will be accessing the database
8:14
so there is no limit in size so this is
8:18
mainly built for the virtual environment
8:22
so data is stored in cloud data is
8:33
stored in cloud and this is mainly built
8:38
for virtual environment virtual
8:46
environment right so this is for our
8:50
cloud database the next one there is
9:07
object-oriented enemies so we know that
9:10
that object-oriented means everything
9:12
will be treated in terms of excuse me
9:15
classes or objects right so here this is
9:20
nothing but the object-oriented
9:24
programming
9:31
plus relational database so this is a
9:40
combination of object-oriented
9:42
programming and the relational database
9:47
right so here everything will be treated
9:55
as objects rather than the actions and
9:59
the relationship is nothing but a data
10:02
other than the logic so maybe everything
10:08
will be in terms of objects objects or
10:12
classes so a combination of
10:14
object-oriented programming plus a
10:16
relational database
10:17
so here the object-oriented programming
10:19
can be achieved with the help of
10:22
languages we had a number of pro
10:25
object-oriented programming languages
10:27
like C++ or Java right so with the help
10:32
of those languages we'll get their
10:34
objects and that is related to the
10:36
relational database and organizing the
10:39
net optimizing a similar way of
10:42
relational database so this is all our
10:44
object-oriented database right and one
10:50
more thing is there that is last one so
10:55
graph database
11:05
graph database so we know that a graph
11:09
is a collection of loops and edges so a
11:13
graph consists of nodes and edges so
11:19
here in this database a node represents
11:22
an entity and actually presents the
11:28
relationship between entities so here a
11:39
node represents the entity single entity
11:41
and the edge represents the relationship
11:44
between a different entities so this is
11:48
how the graph database is organized
11:52
right so these are the different types
11:56
of databases so from the next session
12:00
we'll go with this relational database
12:04
right so how the data is organized in
12:07
tabular form at that position in terms
12:09
of rows and columns so let us stop here
12:13
so these are a few types of databases we
12:17
have covered in this session so if you
12:20
are having any doubts regarding this one
12:22
feel free to post your doubts in the
12:24
comment section so that definitely I'm
12:26
try to clarify all your dots and if you
12:29
really understood my session liked my
12:32
session share my sessions with your
12:33
friends and don't forget to subscribe to
12:36
our channel thanks for watching thank
12:39
you very much