| 1 | 15 | ||||||||||||||||||||||||
| 18 | |||||||||||||||||||||||||
| 14 | 16 | ||||||||||||||||||||||||
| 2 | |||||||||||||||||||||||||
| 3 | |||||||||||||||||||||||||
| 4 | |||||||||||||||||||||||||
| 5 | |||||||||||||||||||||||||
| 13 | 6 | ||||||||||||||||||||||||
| 8 | 7 | ||||||||||||||||||||||||
| 9 | |||||||||||||||||||||||||
| 17 | |||||||||||||||||||||||||
| 10 | 11 | ||||||||||||||||||||||||
| 12 | |||||||||||||||||||||||||
1. A process that reapplies the changes recorded in the transaction log during database recovery.
2. The process of restoring a database to a previous state using the information in the transaction log.
3. The property that ensures that committed transactions survive permanent system failures.
4. The process of determining the order in which transactions should be executed in a database system.
5. Ensuring that the execution of multiple transactions produces the same result as if they were executed sequentially.
6. A specific action carried out on a database.
7. The property that allows multiple transactions to execute concurrently without interfering with each other.
8. A mechanism used to control concurrent access to data, preventing conflicts and ensuring data consistency.
9. The ability to recover a database to a specific moment in time using the transaction log.
10. The process of undoing all changes made within a transaction and returning the database to its previous state.
11. A unit of work performed on a database that follows the ACID approach.
12. A property that determines how concurrent transactions interact with each other and the level of data visibility.
13. A process that reverses the effects of a transaction by applying the opposite changes recorded in the transaction log.
14. A set of properties that guarantee that database transactions are processed reliably.
15. A concurrency control technique in database systems where transactions are ordered based on their timestamp values.
16. The process of performing multiple database operations as a single unit of work, ensuring consistency and integrity of data.
17. The process of recording events, activities, and information to a log file or transaction log.
18. A property of transactions that allows them to behave as if they were executed sequentially, even though they may be executed concurrently.