History of Database

Rules for Database (ACID)

The ACID concept is described in ISO/IEC 10026-1:1992 Section 4. Each of these attributes can be measured against a benchmark. In general, however, a transaction manager or monitor is designed to realize the ACID concept. A program that manages or oversees the sequence of events that are part of a transaction is sometimes called a transaction monitor.

ACID  stands for (atomicity, consistency, isolation, and durability) is an acronym for learning and remembering the four primary attributes ensured to any transaction by a transaction manager (which is also called a transaction monitor). These attributes are:

Atomicity. In a transaction involving two or more discrete pieces of information, either all of the pieces are committed or none are.
Consistency. A transaction either creates a new and valid state of data, or, if any failure occurs, returns all data to its state before the transaction was started.
Isolation. A transaction in process and not yet committed must remain isolated from any other transaction.
Durability. Committed data is saved by the system such that, even in the event of a failure and system restart, the data is available in its correct state.

What is commit: 

Make the changes persistent and visible to other user too, until transaction is not committed changes are only visible to current user. 

What is Rollback: 

In case of any failure all the data should be restored to original state in order to maintain consistency, which ensures that all involved sites must commit to transaction completion or none do, and the transaction is rolled back

Evolution of Database

File system1968 File-Based: predecessor of database, Data was maintained in a flat file.
Flat Files:  Earlier, punched cards technology was used to store data – later, files. But the files have no as such advantage, rather have several limitations.
Hierarchical Data Model:  Mid 1960s Rockwell collaborates with IBM to create the Information Management System (IMS), IMS lead the mainframe database market in 70’s and early 80’s.
In this model, files are related in a parent/child manner, with each child file having at most one parent file.
Network Data Model: Early 1960s, Charles Bachmann developed first DBMS, In Network data model, files are related as owners and members, similar to the common network model except that each member file can have more than one owner.
Network data model identified the following three database components:
1. Network schema—database organization[structure]
2. Sub-schema—view s of database per user
3. Data management language — at low level , procedural

Relational Database and Database Management: The relational database model was conceived by E. F. Codd in 1970. It can be defined using the following two terminologies:
1. Instance – a table with rows or columns.
2. Schema – specifies the structure (name of relation, name and type of each column)
The model is based on branches of mathematics called set theory and predicate logic.
Object Oriented Database Model: It supports the modeling and creation of the data as objects


Database History

1976: Peter Chen defined the Entity-relationship(ER) model
1980s: Maturation of the relational database technology, more relational based DBMS were developed and SQL standard adopted by ISO and ANSI.
1985: Object-oriented DBMS (OODBMS) develops.
1990s: Incorporation of object-orientation in relational DBMSs, new application areas, such as data warehousing and OLAP, web and Internet, Interest in text and multimedia, enterprise resource planning (ERP) and management resource planning (MRP)
1991: Microsoft ships access, a personal DBMS created as element of Windows gradually supplanted all other personal DBMS products.
1995: First Internet database applications


1997: XML applied to database processing, which solves long-standing database problems.  Major vendors begin to integrate XML into DBMS products.


<< BACK HOME >>

No comments:

Post a Comment