Key facts

  • 1970: E. F. Codd published "A Relational Model of Data for Large Shared Data Banks", giving the relational model its formal base.
  • 1975: The ANSI/SPARC architecture described external, conceptual and internal schema levels, a standard frame for data abstraction.
  • 1976: Peter Chen introduced the entity-relationship model, making ER diagrams a standard tool for database design.
  • 1977: Oracle Corporation, first named Software Development Laboratories, was founded and later became a major commercial SQL database vendor.
  • 1983: Theo Haerder and Andreas Reuter used ACID as a transaction property set, now central to DBMS reliability questions.

Key Points at a Glance

  1. 1

    1970: E. F. Codd published "A Relational Model of Data for Large Shared Data Banks", giving the relational model its formal base.

  2. 2

    1975: The ANSI/SPARC architecture described external, conceptual and internal schema levels, a standard frame for data abstraction.

  3. 3

    1976: Peter Chen introduced the entity-relationship model, making ER diagrams a standard tool for database design.

  4. 4

    1977: Oracle Corporation, first named Software Development Laboratories, was founded and later became a major commercial SQL database vendor.

  5. 5

    1983: Theo Haerder and Andreas Reuter used ACID as a transaction property set, now central to DBMS reliability questions.

  6. 6

    1986: ANSI adopted SQL as a standard database language, fixing a common base for SQL syntax and semantics.

  7. 7

    1987: ISO adopted SQL, giving the language international standard status for relational database systems.

  8. 8

    1992: SQL-92 became a major revision that expanded constraints, joins, data types and portable relational database features.

DBMS Purpose and Data Abstraction

A database management system is software that stores, organises, retrieves and protects data for many users and applications. In recruitment-level questions, DBMS is contrasted with the traditional file-processing system. File systems commonly suffer from redundancy, inconsistency, poor sharing, difficult security control and weak recovery after failure. A DBMS solves these by keeping a managed database, a data dictionary, query processing, authorisation rules, backup and recovery facilities, and transaction management in one controlled environment.

The ANSI/SPARC three-schema architecture is a high-yield frame. The internal level describes physical storage, indexes and access paths. The conceptual level describes the whole logical database, including entities, attributes, relationships and constraints. The external level describes user views, so one clerk, teacher or analyst may see only a relevant slice. Physical data independence means changing storage without changing the logical design; logical data independence means changing the conceptual schema without breaking external views. A Rajasthan recruitment portal, for example, can expose separate views for applicant status, payment reconciliation and centre allocation while protecting the same core records.

Exam cue: DBMS questions often test the difference between stored data, metadata, schema, instance, data independence and the weakness of ordinary files.

Open the complete note

This public page shows the first available section. The study pack opens the complete topic with all revision material.

7 more sections in the complete note

Open study pack