Types of DBMS

Database Management Systems

All of us know that, a Database is a collection of records. Database management systems are designed for managing all the records. Database Management is a software system that uses a standard method and running queries with some of them designed for the oversight and proper control of databases.

Types of Database Management Systems:

There are four structural types of database management systems:

• Hierarchical databases.
• Network databases.
• Relational databases.
• Object-oriented databases

Hierarchical Databases  :

It is very fast and simple. In a hierarchical database, records contain information about there groups of parent/child relationships, just like as  a tree structure. The structure implies that a record can have also a repeating information. In this structure Data follows a series of records, It is a set of field values attached to it. It collects all  records together as a record type. These record types are the equivalent of tables in the relational model, and with the individual records being the equivalent of rows. To create links between these record types, the hierarchical model uses these type Relationships.

Network Database  :

A network databases are mainly used on a large digital computers. It more connections can be made between different types of data, network databases are considered more efficiency It contains limitations must be considered when we have to use this kind of database. It is Similar to the hierarchical databases, network databases .Network databases are similar to hierarchical databases by also having a hierarchical structure. A network database looks more like a cobweb or interconnected network of records.

In network databases, children are called members and parents are called occupier. The difference between each child or member can have more than one parent.

Object-Oriented Model  :

In this Model we have to discuss the functionality of the object oriented Programming .It takes more than  storage of programming language objects. Object DBMS's increase the semantics of the C++ and Java .It provides full-featured database programming capability, while containing native language compatibility. It adds the database functionality to object programming languages.This approach is the analogical of the application and database development into a constant data model and language environment. Applications require less code, use more natural data modeling, and code bases are easier to maintain. Object developers can write complete database applications with a decent amount of additional effort.

The object-oriented database derivation is the integrity of object-oriented programming language systems and consistent systems. The power of the  object-oriented databases comes from the cyclical treatment of both consistent data, as found in databases, and transient data, as found in executing programs.

Relational Databases  :

In relational databases, the relationship between data files is relational. Hierarchical and network databases require the user to pass  a hierarchy in order to access needed data. These databases connect to the data in different files by using common data numbers or a key field. Data in relational databases is stored in different access control tables, each having a key field that mainly identifies each row. In the relational databases are more reliable than either the hierarchical or network database structures. In relational databases, tables or files filled up with data are called relations (tuples) designates a row or record, and columns are referred to as attributes or fields.

Relational databases work on each table has a key field that uniquely indicates each row, and that these key fields can be used to connect one table of data to another.

Database Design

Introduction

Database Design is the step by step process of producing a detailed Data Model of a Database. This Logical Data Model contains all the needed Logical and Physical Design choices and physical storage parameters needed to generate a design in a Data Definition Language, which can then be used to create a Database. A fully attributed Data Model contains detailed attributes for each entity.

The term Database Design can be used to describe many different parts of the design of an overall Database System. Principally, and most correctly, it can be thought of as the Logical Design of the base Data Structures used to store the data. In the Relational Model these are the Tables and Views. In an Object Database the entities and relationships map directly to object classes and named relationships. However, the term Database Design could also be used to apply to the overall process of designing, not just the base Data Structures, but also the forms and queries used as part of the overall Database application within the Database Management System (DBMS).

The process of doing Database Design generally consists of a number of steps which will be carried out by the database designer. Usually, the designer must:

• Determine the relationships between the different data elements.
• To add as a distinct feature, element, or quality a logical structure upon the data on the basis of these relationships.
  
  
  
  
  
  DATABASE DESIGN BASICS :

A properly designed database provides you with access to up-to-date, accurate information. Because a correct design is essential to achieving your goals in working with a database, investing the time required to learn the principles of good design makes sense. In the end, you are much more likely to end up with a database that meets your needs and can easily accommodate change. 

This article provides guidelines for planning a database. You will learn how to decide what information you need, how to divide that information into the appropriate tables and columns, and how those tables relate to each other. You should read this article before you create your first database.

Design process :

1. Determine the purpose of the database.
2. Find and organize the information required.
3. Divide the information into tables.
4. Turn information items into columns.
5. Specify primary keys.
6. Set up the table relationships.
7. Refine the design
8. Apply the normalization rules.