Find papers

IT 232

Database Management System

TU BBM · Semester 6 · BBM curriculum effective from 2021

Requirement
required
Credits
3
Study Guide
6 units available

Chapter notes

Authoritative study guide across 6 syllabus units

Open a unit to read its study notes.

Unit 1: Database Concepts and Architecture· 5 LHs· ~6 marks

Suggest correction

Difficulty: ★★★ | High-yield focus: Define DBMS, state its advantages over traditional file systems, and outline the ANSI/SPARC 3-schema architecture. Key exam mastery: Analyze data abstraction layers, DBMS catalog metadata architecture, and physical vs. logical data independence mechanisms.

Part 1: Core Concepts (2 Marks)

Academic Definition of Database and DBMS

A Database (★) is an organized, logically coherent collection of related data with some inherent meaning, designed to be shared across multiple users and applications.

A Database Management System (DBMS) is a complex software system that facilitates the processes of defining, constructing, manipulating, and sharing databases among various users and application programs.

Schema vs. Instance

  • Database Schema: The overall logical structural design of the database (the blueprint), which is rarely modified.
  • Database Instance (State): The actual collection of data stored in the database at a specific, discrete moment in time.

Data Independence Types

  1. Logical Data Independence: The capacity to change the conceptual schema without having to change external schemas or rewrite application programs.
  2. Physical Data Independence: The capacity to modify the internal physical storage schema (indexes, file organization, hard drives) without having to alter the conceptual schema.

Part 2: Structural Frameworks (10 Marks)

ANSI SPARC Three Schema Architecture

ANSI SPARC Three Schema Architecture
ANSI SPARC Three Schema Architecture

1. The ANSI/SPARC Three-Schema Architecture

External External External
Schema Schema Schema

2. Client/Server DBMS Architecture: 2-Tier vs. 3-Tier

  • Two-Tier Architecture: Client machines run the Application User Interface and direct SQL queries directly over a local network to the Database Server. Plagued by security and deployment hurdles when scaling.
  • Three-Tier Architecture (Modern Web):
    Client Web Browser⟷Application / Web Server (Logic)⟷Database Server (Data)\text{Client Web Browser} \longleftrightarrow \text{Application / Web Server (Logic)} \longleftrightarrow \text{Database Server (Data)}
    Application business logic is centralized on the middle tier, decoupling the database from direct public exposure and maximizing enterprise scalability.

Part 3: Distinction Tables

Comparison: Logical vs. Physical Data Independence

Basis of Comparison Logical Data Independence Physical Data Independence
Level of Architecture Operates between Conceptual Schema and External Views. Operates between Internal Schema and Conceptual Schema.
Typical Alteration Adding a new entity, creating a new attribute, or splitting tables. Upgrading from HDD to NVMe SSD, rebuilding B-Tree indexes.
Implementation Difficulty Substantially harder to achieve because application code often embeds data structures. Easier to achieve; handled transparently by the storage engine.

Part 4: Worked Problems & Exam Traps

Common Board Exam Trap: Never confuse a Schema with an Instance. An exam question asking to “Differentiate between schema and state” is asking for Blueprint (Schema) vs. Current Content (State/Instance).

Students lose marks here because they describe the three-schema architecture without explaining physical data independence versus logical data independence.