Dbms titles short notes, Cheat Sheet of Database Management Systems (DBMS)

Dbms - Dbms titles short notes

Typology: Cheat Sheet

2024/2025

Uploaded on 09/10/2025

gopikaa-jaisankar
gopikaa-jaisankar 🇺🇸

1 document

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Database Systems – Exam 1
Complete Study Guide
Syllabus: Chapters 1, 2, 3 (except 3.8), 4 (except 4.6) from Elmasri &
Navathe, Fundamentals of Database Systems (7th Edition).
Chapter 1 – Databases and Database Users
- **Definition of Database**: A collection of related data representing some
aspect of the real world (mini-world).
- **DBMS**: Software to define, construct, manipulate, and share databases.
Functions: defining schema, querying, updating, backup, concurrency
control, security.
- **Database System** = Database + DBMS software.
- **Metadata**: Data about data (schemas, constraints) stored in catalog.
- **Main Characteristics**:
1. Self-describing (catalog with schema & constraints)
2. Program-data independence (data abstraction)
3. Multiple views of data (different subsets for different users)
4. Multi-user transaction processing (concurrency control, OLTP)
- **Advantages of DBMS**: controls redundancy, ensures consistency,
restricts unauthorized access, persistent storage, backup & recovery.
- **People around DBMS**:
- Actors on the scene: DBA, Designers, Users (casual, naïve, sophisticated,
standalone), Application programmers.
- Workers behind the scene: DBMS designers, tool developers, operators,
maintenance staff.
- **When Not to Use DBMS**: high overhead, simple one-user applications,
real-time constraints not met, very high initial cost.
Chapter 2 – Database System Concepts and
Architecture
- **Data Models**:
- High-level/Conceptual: ER, EER (easy for humans).
- Representational: Relational model (tables).
- Low-level/Physical: how data stored on disk.
- **Schemas vs Instances**:
pf3

Partial preview of the text

Download Dbms titles short notes and more Cheat Sheet Database Management Systems (DBMS) in PDF only on Docsity!

Database Systems – Exam 1

Complete Study Guide

Syllabus: Chapters 1, 2, 3 (except 3.8), 4 (except 4.6) from Elmasri & Navathe, Fundamentals of Database Systems (7th Edition).

Chapter 1 – Databases and Database Users

  • Definition of Database: A collection of related data representing some aspect of the real world (mini-world).
  • DBMS: Software to define, construct, manipulate, and share databases. Functions: defining schema, querying, updating, backup, concurrency control, security.
  • Database System = Database + DBMS software.
  • Metadata: Data about data (schemas, constraints) stored in catalog.
  • Main Characteristics:
    1. Self-describing (catalog with schema & constraints)
    2. Program-data independence (data abstraction)
    3. Multiple views of data (different subsets for different users)
    4. Multi-user transaction processing (concurrency control, OLTP)
  • Advantages of DBMS: controls redundancy, ensures consistency, restricts unauthorized access, persistent storage, backup & recovery.
  • People around DBMS:
    • Actors on the scene: DBA, Designers, Users (casual, naïve, sophisticated, standalone), Application programmers.
    • Workers behind the scene: DBMS designers, tool developers, operators, maintenance staff.
  • When Not to Use DBMS: high overhead, simple one-user applications, real-time constraints not met, very high initial cost.

Chapter 2 – Database System Concepts and

Architecture

  • Data Models:
    • High-level/Conceptual: ER, EER (easy for humans).
    • Representational: Relational model (tables).
    • Low-level/Physical: how data stored on disk.
  • Schemas vs Instances:
  • Schema = blueprint (intension).
  • Instance = current snapshot (extension).
  • Three-Schema Architecture (ANSI/SPARC):
  • Internal schema: storage, indexes.
  • Conceptual schema: overall logical structure.
  • External schema: user views.
  • Data Independence:
  • Physical: change storage w/o affecting schema.
  • Logical: change schema w/o affecting views.
  • Database Languages: DDL, DML, SDL, VDL.
  • Interfaces: Menu, forms, GUIs, natural language.
  • DBMS Architectures: centralized vs client-server, multi-tier.
  • Classification: single-user/multi-user, centralized/distributed, homogeneous/heterogeneous.

Chapter 3 – Data Modeling Using ER Model

  • Entities:
    • Entity = real-world object.
    • Entity set = group of entities.
    • Attributes:
      • Simple (atomic), Composite (can be divided), Multi-valued (many values), Derived (calculated).
    • Keys: uniquely identify entity (primary key, candidate keys).
  • Relationships:
    • Degree: unary, binary, ternary, n-ary.
    • Cardinality ratios: 1:1, 1:N, M:N.
    • Participation: total (must exist), partial (optional).
    • Roles clarify involvement in relationships.
  • Weak Entities:
    • Cannot be uniquely identified by own attributes.
    • Need owner entity + partial key + identifying relationship.
  • Design Issues: naming conventions, clarity, avoiding redundancy.

Chapter 4 – Enhanced ER (EER) Model

  • Superclass & Subclass:
    • Superclass: general entity type.
    • Subclass: specific entity type.
    • Inheritance: subclass inherits attributes and relationships from