Hierarchical and Network Data Models in DBMS

Hierarchical Model
One of the earliest models of a data model created by IBM in the 1950s is this one.
Data are viewed as a group of tables, or segments that create a hierarchical relation, in
a hierarchical model. A tree-like structure is used to arrange data in a hierarchical
form, with each record having many offspring and many parents.
The physical arrangement of records in storage is determined by the hierarchical
structure. Using pointers and sequential accessing together, one can go around the data
structure to reach the records. As a result, when a full path is not additionally given for
each entry, the hierarchical structure is not appropriate for some database operations.
This construction is straightforward but rigid because the interaction is limited to
one-to-many interactions. This model's fundamental flaw is that it can only support
one-to-many relationships between nodes.

Advantage of Hierarchical Model

-Data security is provided, and this paradigm was the first database model to do so.
Because there are clear relationships between the table structures, a user can obtain
data relatively rapidly.
-Data integrity is also present since it is based on the parent-child relationship and
because the segments for parents and children are always connected.
-A record in a child table must be linked to an existing record in the parent table
because referential integrity is built into and automatically enforced. In addition, if a
record is deleted from the parent table, all associated records in the child table will
also be deleted.

Disadvantage of Hierarchical Model

-This paradigm is also inflexible because the addition of new tables or segments
frequently results in complicated system management duties. In this case, deleting one
segment may force the deletion of every segment that lies behind it.
-Exists a Hierarchical model lacks structural independence
-Storage space wastage.
-The hierarchical navigation system is complicated.
-difficult to design.
-It becomes difficult to record and the user must add another entry to the parent table
when they need to store a record in a child table that is currently unrelated to any
record in the parent table.
Network Model
A database model called a "network model" was created as a flexible method of
expressing things and their connections. It has entities that are arranged graphically,
some of which can be reached by several paths.
The Database Task group defined this paradigm in the 1960s.
The hierarchical model is generalised in this model. Charles Bachman was the original
developer of the network model.
The data in this model is more closely related because there are more relationships. It
has the capacity to control both one-to-one and many-to-many relationships. Due to
numerous relationships, there may be more than one way to reach the same record. It
facilitates quick and easy data access.

Advantages of Network Model

-Compared to a database with a hierarchical database model, the network model
enables the creation of more complex and powerful queries. When choosing the
network model, a user can run a number of different database queries.
-We have easy access to the data in this model, and there is a potential that the
application will also have access to the records of the set's owners and members.
Because a member of this network cannot exist without an owner, the idea of data
integrity is born.
-With a network paradigm, data access is quick.
-Compared to hierarchical models, data access is more flexible and improves database
performance.

Disadvantage of Network Model

-The user must be highly familiar with the overall structure of the database because
the network model is a very complicated database model.
-Despite the network database model's ability to achieve data independence, this
model is unable to achieve structural independence.
-Due to the intricate structure, maintain a lot of strain on the programmers.
-Due to the use of pointers for navigation, which further results in complex
implementation, there are operational abnormalities.
-All application programs must be changed to accommodate structural changes.Any
change, such as an update, deletion, or addition, is quite difficult.