Database Tutorial Home
- Introduction To Database
- Data Models
- Three-Schema Architecture of Database Systems
- Database System Architectures
- Codd\'s Rules for Relational Databases.
- Keys in DBMS
- Concept of Normalization
- First Normal Form
- Second Normal Form
- Third Normal Form
- Boyce-Codd Normal Form(BCNF)
- Fourth Normal Form
- Fifth Normal Form (Projection-Join Normal Form)
- Introduction TO SQL
- Transactions in DBMS
- Steps to Design Database for a System
- Members (1542)
- Member Articles ( 0 )
- Discussion (4)
- Q & A ( 15 )
- - Ask Question
- - Questions
- - Unanswered Questions
Data model is defined as the collection of conceptual tools for describing data, data relationships, data semantics and consistency constraints. There are following four Data Model exists.
The Hierarchical Data Model
A hierarchical database consists of the following:
- It contains nodes connected by branches same as the trees in datastructers.
- The top node is called the root.
- If multiple nodes appear at the top level, the nodes are called root segments.
- The parent of node nx is a node directly above nx and connected to nx by a branch.
- Each node (with the exception of the root) has exactly one parent.
- The child of node nx is the node directly below nx and connected to nx by a branch.
- One parent may have many children.
The Network Data Model
Like the The Hierarchical Data Model the Network Data Model also consists of nodes and branches, but a child may have multiple parents within the network structure.
The Relational Data Model
The Relational Data Model has the relation at its heart, but then a whole series of rules governing keys, relationships, joins, functional dependencies, transitive dependencies, multi-valued dependencies, and modification anomalies. A relation is subject to the following rules:
- Relation (file, table) is a two-dimensional table.
- Attribute (i.e. field or data item) is a column in the table.
- Each column in the table has a unique name within that table.
- Each column is homogeneous. Thus the entries in any column are all of the same type (e.g. age, name, employee-number, etc).
- Each column has a domain, the set of possible values that can appear in that column.
- A Tuple (i.e. record) is a row in the table.
- The order of the rows and columns is not important.
- Values of a row all relate to some thing or portion of a thing.
- Repeating groups (collections of logically related attributes that occur multiple times within one record occurrence) are not allowed.
- Duplicate rows are not allowed (candidate keys are designed to prevent this).
- Cells must be single-valued (but can be variable length). Single valued means the following:
- Cannot contain multiple values such as 'A1,B2,C3'.
- Cannot contain combined values such as 'ABC-XYZ' where 'ABC' means one thing and 'XYZ' another.
Object Oriented Model
In object oriented model information is represented in the form of objects as used in object oriented programming. Object Oriented Database Management Systems is a combination of object oriented programming language capabilities and database capabilities. It contains some properties like transparently persisted data, concurrency control, data recovery, associative queries, and other capabilities. Some object oriented programming languages are Java, C++, .NET, Visual Basic, Python etc. Most object databases also offer some kind of query language, allowing objects to be found by a more declarative programming approach.