| ACID Approach |
A set of properties that guarantee that database transactions are processed reliably. |
| Atomicity |
The property of a transaction to be an indivisible operation, either all or none of its changes are applied. |
| Audit Trail |
A sequential record of all the changes made to a database, stored in the transaction log. |
| Commit |
The final step of a database transaction where all changes made within the transaction are permanently saved. |
| Concurrency |
The property that allows multiple transactions to execute concurrently without interfering with each other. |
| Concurrency Control |
Techniques and mechanisms used to manage the simultaneous execution of transactions without interference or inconsistency. |
| Consistency |
The property that ensures the database remains in a valid state after a transaction. |
| Database Transactions |
The process of performing multiple database operations as a single unit of work, ensuring consistency and integrity of data. |
| Deadlock |
A situation where two or more transactions are unable to proceed because each is waiting for the other to release a resource. |
| Durability |
The property that ensures that committed transactions survive permanent system failures. |
| Isolation |
The property that ensures transactions are executed in a way that they are unaware of each other. |
| Isolation Level |
A property that determines how concurrent transactions interact with each other and the level of data visibility. |
| Locking |
A mechanism used to control concurrent access to data, preventing conflicts and ensuring data consistency. |
| Log File |
A file that contains a systematic record of events, actions, or observations. |
| Logging |
The process of recording events, activities, and information to a log file or transaction log. |
| Operation |
A specific action carried out on a database. |
| Point-In-Time Recovery |
The ability to recover a database to a specific moment in time using the transaction log. |
| Query |
A request for data or information from a database. |
| Record |
A single, complete set of information within a table. |
| Recovery |
The process of restoring a database to a previous state using the information in the transaction log. |
| Redo Log |
A mechanism used in the recovery process of a database to bring it to a consistent state after a crash. |
| Redo Operation |
A process that reapplies the changes recorded in the transaction log during database recovery. |
| Rollback |
The process of undoing all changes made within a transaction and returning the database to its previous state. |
| Savepoint |
A point within a transaction where you can roll back a part of the transaction instead of the entire transaction. |
| Serializability |
A property of transactions that allows them to behave as if they were executed sequentially, even though they may be executed concurrently. |
| Serialization |
Ensuring that the execution of multiple transactions produces the same result as if they were executed sequentially. |
| Timestamp Ordering |
A concurrency control technique in database systems where transactions are ordered based on their timestamp values. |
| Transaction |
A unit of work performed on a database that follows the ACID approach. |
| Transaction Log |
A file that records all the transactions and activities in a database system. |
| Transaction Scheduling |
The process of determining the order in which transactions should be executed in a database system. |
| Two-Phase Locking |
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. |
| Undo Log |
A mechanism used in the recovery process of a database to revert the effects of incomplete or aborted transactions. |
| Undo Operation |
A process that reverses the effects of a transaction by applying the opposite changes recorded in the transaction log. |
