| 1 | 14 | 16 | |||||||||||||||||||||||
| 2/17 | |||||||||||||||||||||||||
| 3 | |||||||||||||||||||||||||
| 4 | |||||||||||||||||||||||||
| 13 | 5 | 19 | |||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 7 | 18 | ||||||||||||||||||||||||
| 8 | 15 | ||||||||||||||||||||||||
| 9 | |||||||||||||||||||||||||
| 10 | |||||||||||||||||||||||||
| 11 | |||||||||||||||||||||||||
| 12 | |||||||||||||||||||||||||
1. A sequential record of all the changes made to a database, stored in the transaction log.
2. 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.
3. The final step of a database transaction where all changes made within the transaction are permanently saved.
4. The process of determining the order in which transactions should be executed in a database system.
5. A file that contains a systematic record of events, actions, or observations.
6. The property that ensures the database remains in a valid state after a transaction.
7. The ability to recover a database to a specific moment in time using the transaction log.
8. The process of undoing all changes made within a transaction and returning the database to its previous state.
9. A mechanism used in the recovery process of a database to revert the effects of incomplete or aborted transactions.
10. A single, complete set of information within a table.
11. A set of properties that guarantee that database transactions are processed reliably.
12. A concurrency control technique in database systems where transactions are ordered based on their timestamp values.
13. The property that allows multiple transactions to execute concurrently without interfering with each other.
14. A property that determines how concurrent transactions interact with each other and the level of data visibility.
15. The property of a transaction to be an indivisible operation, either all or none of its changes are applied.
16. The process of recording events, activities, and information to a log file or transaction log.
17. A unit of work performed on a database that follows the ACID approach.
18. A mechanism used in the recovery process of a database to bring it to a consistent state after a crash.
19. A process that reverses the effects of a transaction by applying the opposite changes recorded in the transaction log.