| 1/2 | 15 | ||||||||||||||||||||||||
| 3 | |||||||||||||||||||||||||
| 18 | |||||||||||||||||||||||||
| 4 | |||||||||||||||||||||||||
| 5 | 16 | ||||||||||||||||||||||||
| 6 | |||||||||||||||||||||||||
| 7 | |||||||||||||||||||||||||
| 8 | |||||||||||||||||||||||||
| 14 | 9 | ||||||||||||||||||||||||
| 10 | 17 | ||||||||||||||||||||||||
| 11 | |||||||||||||||||||||||||
| 12 | |||||||||||||||||||||||||
| 13 | |||||||||||||||||||||||||
1. The property that ensures transactions are executed in a way that they are unaware of each other.
2. A property that determines how concurrent transactions interact with each other and the level of data visibility.
3. A process that reapplies the changes recorded in the transaction log during database recovery.
4. A file that records all the transactions and activities in a database system.
5. The property that ensures that committed transactions survive permanent system failures.
6. The property that allows multiple transactions to execute concurrently without interfering with each other.
7. Ensuring that the execution of multiple transactions produces the same result as if they were executed sequentially.
8. A set of properties that guarantee that database transactions are processed reliably.
9. A concurrency control technique in database systems where transactions are ordered based on their timestamp values.
10. A unit of work performed on a database that follows the ACID approach.
11. The ability to recover a database to a specific moment in time using the transaction log.
12. The process of undoing all changes made within a transaction and returning the database to its previous state.
13. A specific action carried out on a database.
14. A situation where two or more transactions are unable to proceed because each is waiting for the other to release a resource.
15. A sequential record of all the changes made to a database, stored in the transaction log.
16. 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.
17. A point within a transaction where you can roll back a part of the transaction instead of the entire transaction.
18. The process of performing multiple database operations as a single unit of work, ensuring consistency and integrity of data.