Database Ass
Database Ass
Even though this model is conceptually simple and easy to design at the
same time it is quite complex to implement.
This model also lacks flexibility as the changes in the new tables or
segments often yield very complex system management tasks. Here,
a deletion of one segment can lead to the involuntary deletion of all
segments under it.
It has no standards as the implementation of this model does not
provide any specific standard.
It is also limited as many of the common relationships do not
conform to the 1 to N format as required by the hierarchical
model.
2. NETWORK MODEL
Network Model in DBMS
Network Model :
This model was formalized by the Database Task group in the 1960s. This
model is the generalization of the hierarchical model. This model can consist
of multiple parent segments and these segments are grouped as levels but
there exists a logical association between the segments belonging to any
level. Mostly, there exists a many-to-many logical association between any of
the two segments. We called graphs the logical associations between the
segments. Therefore, this model replaces the hierarchical tree with a graph-
like structure, and with that, there can more general connections among
different nodes. It can have M: N relations i.e, many-to-many which allows a
record to have more than one parent segment.
Here, a relationship is called a set, and each set is made up of at least 2 types
of record which are given below:
This model is very simple and easy to design like the hierarchical data
model.
This model is capable of handling multiple types of relationships which
can help in modeling real-life applications, for example, 1: 1, 1: M, M:
N relationships.
In
this model, we can access the data easily, and also there is a chance
that the application can access the owner’s and the member’s records
within a set.
This network does not allow a member to exist without an owner which
leads to the concept of Data integrity.
Like a hierarchical model, this model also does not have any database
standard,
Disadvantages of Network Model :
The
schema or the structure of this database is very complex in nature
as all the records are maintained by the use of pointers.
There’s an existence of operational anomalies as there is a use of
pointers for navigation which further leads to complex implementation.
The design or the structure of this model is not user-friendly.
This model does not have any scope of automated query optimization.
This model fails in achieving structural independence even though the
network database model is capable of achieving data independence.
3. SEMI STRUCTURE DATA MODEL.
Semi-structured data[1] is a form of structured data that does not obey the
tabular structure of data models associated with relational databases or
other forms of data tables, but nonetheless contains tags or other markers to
separate semantic elements and enforce hierarchies of records and fields
within the data. Therefore, it is also known as self-describing structure.
In semi-structured data, the entities belonging to the same class may have
different attributes even though they are grouped together, and the
attributes' order is not important.
Semi-structured data are increasingly occurring since the advent of
the Internet where full-text documents and databases are not the only forms
of data anymore, and different applications need a medium for exchanging
information. In object-oriented databases, one often finds semi-structured
data.
The semi-structured model is a database model where there is no
separation between the data and the schema, and the amount of structure
used depends on the purpose.
The advantages of this model are the following: