| 1/10 | 11 | 13 | 15 | 17 | |||||||||||||||||||||
| 2 | |||||||||||||||||||||||||
| 3 | 19 | ||||||||||||||||||||||||
| 18 | |||||||||||||||||||||||||
| 4 | |||||||||||||||||||||||||
| 16 | |||||||||||||||||||||||||
| 5/6 | 14 | ||||||||||||||||||||||||
| 12 | |||||||||||||||||||||||||
| 9 | |||||||||||||||||||||||||
| 7 | |||||||||||||||||||||||||
| 8 | |||||||||||||||||||||||||
1. A file that records all the transactions and activities in a database system.
2. A point within a transaction where you can roll back a part of the transaction instead of the entire transaction.
3. A sequential record of all the changes made to a database, stored in the transaction log.
4. The property that allows multiple transactions to execute concurrently without interfering with each other.
5. A unit of work performed on a database that follows the ACID approach.
6. The process of determining the order in which transactions should be executed in a database system.
7. A specific action carried out on a database.
8. The property that ensures transactions are executed in a way that they are unaware of each other.
9. A mechanism used to control concurrent access to data, preventing conflicts and ensuring data consistency.
10. A concurrency control technique in database systems where transactions are ordered based on their timestamp values.
11. A set of properties that guarantee that database transactions are processed reliably.
12. The process of restoring a database to a previous state using the information in the transaction log.
13. A property of transactions that allows them to behave as if they were executed sequentially, even though they may be executed concurrently.
14. The property of a transaction to be an indivisible operation, either all or none of its changes are applied.
15. The property that ensures the database remains in a valid state after a transaction.
16. A process that reverses the effects of a transaction by applying the opposite changes recorded in the transaction log.
17. The property that ensures that committed transactions survive permanent system failures.
18. The process of performing multiple database operations as a single unit of work, ensuring consistency and integrity of data.
19. The ability to recover a database to a specific moment in time using the transaction log.