Which of the following is not a property of a transaction in a DBMS?Select one:a. Isolationb. Atomicityc. Consistencyd. Uniqueness
Question
Which of the following is not a property of a transaction in a DBMS?Select one:a. Isolationb. Atomicityc. Consistencyd. Uniqueness
Solution
The correct answer is d. Uniqueness.
In the context of a DBMS (Database Management System), a transaction must have the following properties, often referred to as ACID properties:
a. Atomicity: This means that a transaction must be treated as a single, indivisible unit of work. In other words, either all of its data modifications are performed, or none of them are.
b. Consistency: This ensures that a transaction brings the database from one valid state to another. The database should satisfy a specific set of constraints before and after the transaction.
c. Isolation: This property ensures that the concurrent execution of transactions results in a system state that would be obtained if transactions were executed serially, i.e., one after the other.
However,
d. Uniqueness: This is not a property of a transaction in a DBMS. Uniqueness is a property that can be set on a database column to ensure that no two rows in the table can have the same value in that column. But it's not a property of the transaction itself.
Similar Questions
To support concurrent transactions, a DBMS should have which of the following properties?Select one:a.atomicity, durability, and isolationb.atomicity, irreducibility, and isolationc.durability, irreducibility, and isolationd.atomicity, durability, and irreducibility
Discuss Consistency and Isolation property of a transaction
Which of the following properties ensures that once a transaction commits, its results are permanent?Question 12Select one:A.FlexibilityB.DurabilityC.IsolationD.AtomicityE.Consistency
What does the isolation property of transactions aim to prevent?Hardware failuresData inconsistenciesConcurrent access issuesDatabase corruptionReview AnswerNext
Atomicity. A transaction is an atomic unit of processing; it should either beperformed in its entirety or not performed at all.■ Consistency preservation. A transaction should be consistency preserving,meaning that if it is completely executed from beginning to end withoutinterference from other transactions, it should take the database from oneconsistent state to another.■ Isolation. A transaction should appear as though it is being executed in iso-lation from other transactions, even though many transactions are executing7Undo and redo are discussed more fully in Chapter 23.21.4 Characterizing Schedules Based on Recoverability 755concurrently. That is, the execution of a transaction should not be interferedwith by any other transactions executing concurrently.■ Durability or permanency. The changes applied to the database by a com-mitted transaction must persist in the database. These changes must not belost because of any failure.
Upgrade your grade with Knowee
Get personalized homework help. Review tough concepts in more detail, or go deeper into your topic by exploring other relevant questions.