Database Management Systems
Unit 1: Introduction to Database Systems
From file-system chaos to relational elegance — understand why databases power every ₹ transaction, every Aadhaar lookup, and every Swiggy order you place.
🏢 Oracle & PostgreSQL | 📝 15 MCQs (Bloom's) | 🔬 5 Lab Exercises | 💼 Interview Prep
Why This Chapter Pays Your Salary
Every application you've ever used — Swiggy, PhonePe, IRCTC, Instagram — is a pretty front-end sitting on top of a database. The front-end is what users see. The database is where the money lives. If the database goes down, the business goes down. Database skills are the highest-paid, most durable skills in IT. Oracle DBAs at Indian banks earn ₹18-35 LPA. Understanding databases is not optional — it's the foundation of every software system.
🏢 Industry Snapshot
SBI (State Bank of India) — Operates one of Asia's largest Oracle databases. Their Core Banking Solution (CBS) processes 100+ crore transactions monthly across 22,000 branches. Every rupee passing through India's largest bank touches Oracle DB.
UIDAI (Aadhaar) — Stores biometric + demographic data for 1.4 billion Indians. The world's largest biometric database uses a combination of Oracle, PostgreSQL, and custom NoSQL stores. 10+ billion authentication transactions since launch.
Flipkart — Product catalog (50 crore+ items), customer data, order history, seller inventory — all managed by a combination of PostgreSQL, MySQL, and Redis. Their database architecture handles 10 lakh+ orders on Big Billion Days.
Learning Outcomes — Bloom's Taxonomy
| Bloom's Level | Outcome Statement |
|---|---|
| L1 — Remember | List the limitations of file-based systems, name DBMS components, and recall the properties of a relation |
| L2 — Understand | Explain the three-schema architecture (ANSI/SPARC), differentiate between logical and physical data independence, and describe ER model concepts |
| L3 — Apply | Draw ER diagrams for given business domains with correct notation for entities, attributes, relationships, cardinality, and participation |
| L4 — Analyze | Compare data models (hierarchical, network, relational, document) and analyze when to use each; identify candidate keys and superkeys from functional dependencies |
| L5 — Evaluate | Justify the choice of relational model over alternatives for a given Indian enterprise scenario; critique an ER diagram for design flaws |
| L6 — Create | Design a complete ER diagram and map it to a relational schema with all key types for a multi-module business system (hospital, e-commerce, banking) |