1. File Organization
2. Transaction
2.1. Recovery
2.1.1. Log based Recovery
2.1.1.1. Deferred modification technique
2.1.1.2. Immediate modification technique
2.2. ACID property
2.2.1. Atomicity
2.2.2. Consistency
2.2.3. Isolation
2.2.4. Durability
3. Concurrency Control
3.1. Serializability
3.1.1. Serializable Schedule
3.1.1.1. Conflict Serializable
3.1.1.1.1. IF No Conflict Serializable
3.1.1.2. View Serializable
3.1.2. Non-Serializable
3.2. Concurrency Control Techniques
3.2.1. Lock Based Protocol
3.2.1.1. 2-phase locking Protocol
3.2.1.1.1. 2 Phase
3.2.1.1.2. Strict 2-phase locking Protocol Requirements
3.2.1.1.3. Strict 2-phase locking Protocol Property
3.2.1.1.4. Advantages
3.2.1.1.5. Lock starting of transactions with same variable / Conservative 2-PL
3.2.1.2. Lock Upgradation / Downgradation
3.2.1.2.1. Upgradation
3.2.1.2.2. Downgradation
3.2.1.2.3. Advantages
3.2.2. Tree Protocol
3.2.2.1. Advantages
3.2.2.1.1. ensure Conflict Serializable
3.2.2.1.2. Deadlock Free
3.2.2.1.3. Unlock anyTime
3.2.2.1.4. More Concurrency than 2-Phase Locking
3.2.2.2. Disadvantages
3.2.2.2.1. Cascading Rollback
3.2.2.3. Can't be Cyclic
3.2.3. Time-Stamp Protocol
3.2.3.1. 2-Data item
3.2.3.1.1. R-timestamp(X)
3.2.3.1.2. W-timestamp(X)
3.2.3.2. Issues
3.2.3.2.1. Ti issue Read(X)
3.2.3.2.2. Ti issue Write(X)
3.2.3.3. If wounded-wait -> No Starvation -> No Deadlock
3.2.3.4. Advantages
3.2.3.4.1. ensure Serializable
3.2.3.4.2. Free from Deadlock
3.2.3.5. DiaAdvantage
3.2.3.5.1. Starvation
3.2.3.6. THOMAS Write Rule
3.2.3.6.1. Ignore outdated writes
3.2.3.6.2. Its View Serializable with Blind Write . BCZ Blind write Won't Be Conflict Serial
3.2.4. Multiple Granularity
3.2.4.1. 4 Level
3.2.4.1.1. Database
3.2.4.1.2. Region
3.2.4.1.3. File
3.2.4.1.4. Record
3.2.4.2. Intention Mode Lock
3.2.4.2.1. S [Shared]
3.2.4.2.2. X [Exclusive]
3.2.4.2.3. IS [Intension Shared]
3.2.4.2.4. IX [Intension Exclusive]
3.2.4.2.5. SIX [Shared & Intension Exclusive]
3.2.4.3. Advantages
3.2.4.3.1. Enhance Concurrency
3.3. Summary
3.3.1. Cascade Rollback & Cascade Abort is same
3.3.2. Dirty Read may be cause of Cascading abort
3.3.3. Schedule that avoid Cascading abort are Recoverable
3.3.4. All Schedule ⊃ Recoverable ⊃ Cascadeless Recoverable ⊃ Strict