WWW Geeksforgeeks Org Network Model in Dbms
WWW Geeksforgeeks Org Network Model in Dbms
In the above figure, member TWO has only one owner ‘ONE’ whereas member FIVE has two owners i.e, TWO and THREE. Here, each link between
the two record types represents 1 : M relationship between them. This model consists of both lateral and top-down connections between the
nodes. Therefore, it allows 1: 1, 1 : M, M : N relationships among the given entities which helps in avoiding data redundancy problems as it
supports multiple paths to the same record. There are various examples such as TOTAL by Cincom Systems Inc., EDMS by Xerox Corp., etc.
So, in a network model, a one-to-many (1: N) relationship has a link between two record types. Now, in the above figure, SALES-MAN,
CUSTOMER, PRODUCT, INVOICE, PAYMENT, INVOICE-LINE are the types of records for the sales of a company. Now, as you can see in the given
figure, INVOICE-LINE is owned by PRODUCT & INVOICE. INVOICE has also two owners SALES-MAN & CUSTOMER.
Let’s see another example, in which we have two segments, Faculty and Student. Say that student John takes courses both in CS and EE
departments. Now, find how many instances will be there?
For the above example, a student’s instance can have at least 2 parent instances therefore, there exist relations between the instances of students
and faculty segment. The model can be very complex as if we use other segments say Courses and logical associations like Student-Enroll and
Faculty-course. So, in this model, a student can be logically associated with various instances of Faculties and Courses.
Relationships One-to-many (single parent, multiple children) Many-to-many (multiple parents and children)
Redundancy Higher redundancy due to rigid hierarchy Lower redundancy due to shared relationships
Complexity Simpler to design and implement More complex to design and manage
Usage Scenario Suitable for simple, hierarchical data structures Suitable for complex, interconnected data structures
Efficiency Efficient for hierarchical traversal Efficient for complex queries and data retrieval
Conclusion
The network model in DBMS offers a flexible way to represent complex data relationships through its graph-based structure. While it allows for
many-to-many relationships and more intricate data connections compared to the hierarchical model, it also requires more sophisticated
navigational access methods. Understanding its features and operations helps in leveraging its capabilities for scenarios that involve complex data
interactions.
Frequently Asked Questions on Network Model in DBMS – FAQ’s
The network model’s primary advantages include its ability to handle many-to-many relationships and represent complex data structures. It
also provides efficient navigational access to data through predefined paths.
The network model maintains data integrity through its owner-member relationships, ensuring that changes in one part of the database
appropriately cascade to related records. This helps preserve consistency across the database.
The network model is particularly useful in applications that require complex relationships between data entities, such as
telecommunications, transportation networks, and inventory management systems. It is also beneficial in scenarios where efficient
navigational access is crucial.
"GeeksforGeeks helped me ace the GATE exam! Whenever I had any doubt regarding any topic, GFG always helped me and made my concepts
quiet clear." - Anshika Modi | AIR 21
Choose GeeksforGeeks as your perfect GATE 2025 Preparation partner with these newly launched programs
GATE CS & IT- Online
GATE DS & AI- Online
Over 150,000+ students already trust us to be their GATE Exam guide. Join them & let us help you in opening the GATE to top-tech IITs & NITs!
tarun… 18
Next Article
Relational Model in DBMS
Similar Reads
Difference between E-R Model and Relational Model in DBMS
In database management systems (DBMS), two key methods are the Relational model and the Entity-Relationship (E-R) model. Each has a specific
function in the development and operation of databases. While the Relational model provides the practical structure for organizing and managing data i…
3 min read
Starvation in DBMS
Starvation or Livelock is the situation when a transaction has to wait for an indefinite period of time to acquire a lock. Reasons for Starvation:If the waiting
scheme for locked items is unfair. ( priority queue )Victim selection (the same transaction is selected as a victim repeatedly )Resource leak.Via denial-of-…
5 min read
Tuple in DBMS
Pre-requisites: Introduction of DBMS A tuple, also known as a record or row, is a basic unit of data in a relational database management system (DBMS).
A tuple represents a single instance of a relation, or table, in the database. Each tuple contains a set of values, or attributes, that correspond to the…
4 min read
Interfaces in DBMS
A database management system (DBMS) interface is a user interface that allows for the ability to input queries to a database without using the query
language itself. User-friendly interfaces provided by DBMS may include the following: Menu-Based InterfacesForms-Based InterfacesGraphical User…
4 min read
Company Languages
About Us Python
Legal Java
In Media C++
Contact Us PHP
Advertise with us GoLang
GFG Corporate Solution SQL
Placement Training Program R Language
GeeksforGeeks Community Android Tutorial
Tutorials Archive