Answer: Entity Set
Answer: Natural Join
Answer: Hierarchical Schema
Answer: Google
Answer: Code Penetration Technique
Answer: The size of a data item (unit of locking).
Answer: Data Manipulation Language (DML)
Answer: How data is used
Answer: Strong Entity Set
Answer: Transaction Control Language
Answer: All of the above
Answer: Referential Integrity Constraint
Atomicity: all-or-nothing; Consistency: valid state; Isolation: concurrent txns don't interfere; Durability: committed changes persist. Example: Bank transfer: debit & credit both occur or none.
| Locking Protocol | Timestamp Protocol |
|---|---|
| Uses locks, may cause deadlock | Uses timestamps, deadlock free |
| Transactions wait | Transactions abort/restart |
| Example: 2PL | Example: Timestamp Ordering |
Rule-based optimization: early selection/projection, replace Cartesian product with join, reduce intermediate results β faster execution, lower memory.
Abstraction levels: Physical, Logical, View. DBA: user management, security, backup/recovery, performance tuning, schema management, authorization.
Insertion anomaly: can't insert without related data. Deletion anomaly: removing one deletes useful info. Update anomaly: inconsistency due to duplication.
Entities: Supplier (Sup_ID PK, Name, Address), Item (Item_Type PK, Description). Relationship Supplies with attributes: Quantity, Price. Cardinality: M:N.
Final B-Tree: Root [20]; left child [10,15]; right child [35]; leaves: [8],[12],[18],[30],[38,50].
Atomicity, Consistency, Isolation, Durability. Example: money transfer ensures both debit/credit or none; after commit, data persists.
Wait-Die: older waits, younger dies. Wound-Wait: older wounds (aborts) younger. Both prevent deadlock in concurrency control.
Data only in leaves, internal nodes contain search keys, leaves linked. Example: root [20|40] β leaves [10],[30],[50]. Advantages: fast search, efficient range queries.
Reduces time, disk access, memory. Steps: parsing β translation β optimization β plan generation β execution. Heuristic uses rules (e.g., early selection).
Levels: Database, Table, Page, Record, Field. Fine granularity β better concurrency, coarser β less overhead.
Methods: Wait-Die, Wound-Wait, Timeout, Resource Ordering. Prevents circular wait, improves concurrency.
5NF: eliminates join dependency. View: virtual table. Trigger: automatic procedure on event. Recovery: restores via logs/checkpoints. Problems: lost update, dirty read, unrepeatable read, phantom. 2PL: growing + shrinking phases β serializability. Cursor: row-by-row processing.
T1: Lock-X(A), Read(A), A=A-500, Write(A), Lock-X(B), Read(B), B=B+500, Write(B), Unlock(A), Unlock(B), Commit. T2: Lock-S(A), Read(A), Lock-S(B), Read(B), Display, Unlock(A), Unlock(B). Follows 2PL (all locks before release).
| DAC (Discretionary) | MAC (Mandatory) |
|---|---|
| Owner controlled, GRANT/REVOKE | System controlled by security levels |
| Flexible, less secure | Strict, more secure (military) |
β Complete coverage of MAKAUT DBMS (PCC-CS601) 2023β24 β all groups.
β Includes ER diagram, relational algebra, hierarchical schema, SQL injection, granularity, DML, ACID, locking vs timestamp, heuristics, data abstraction, anomalies, B-Tree/B+Tree, Wait-Die/Wound-Wait, query optimization, 2PL, DAC/MAC, and short notes.
β Answers structured for 1, 5, and 15-mark questions with clear headings & exam-style presentation.