| 1/13 | |||||||||||||||||||||
| 18 | |||||||||||||||||||||
| 2 | 14 | 19 | |||||||||||||||||||
| 3 | |||||||||||||||||||||
| 4/5 | |||||||||||||||||||||
| 7 | 6 | ||||||||||||||||||||
| 8 | 16 | ||||||||||||||||||||
| 17 | |||||||||||||||||||||
| 9 | |||||||||||||||||||||
| 15 | |||||||||||||||||||||
| 11 | 10 | ||||||||||||||||||||
| 12 | |||||||||||||||||||||
1. A concurrency control protocol where a transaction acquires all its required locks before starting execution and releases them all at the end. It enforces serializability.
2. A property of transactions that allows them to behave as if they were executed sequentially, even though they may be executed concurrently.
3. A situation where two or more transactions are unable to proceed because each is waiting for the other to release a resource.
4. The property that ensures transactions are executed in a way that they are unaware of each other.
5. A property that determines how concurrent transactions interact with each other and the level of data visibility.
6. The process of recording events, activities, and information to a log file or transaction log.
7. The process of restoring a database to a previous state using the information in the transaction log.
8. A unit of work performed on a database that follows the ACID approach.
9. The property that allows multiple transactions to execute concurrently without interfering with each other.
10. A specific action carried out on a database.
11. A mechanism used in the recovery process of a database to revert the effects of incomplete or aborted transactions.
12. The property that ensures the database remains in a valid state after a transaction.
13. A file that records all the transactions and activities in a database system.
14. A process that reapplies the changes recorded in the transaction log during database recovery.
15. The final step of a database transaction where all changes made within the transaction are permanently saved.
16. A point within a transaction where you can roll back a part of the transaction instead of the entire transaction.
17. The process of undoing all changes made within a transaction and returning the database to its previous state.
18. Techniques and mechanisms used to manage the simultaneous execution of transactions without interference or inconsistency.
19. The ability to recover a database to a specific moment in time using the transaction log.