You are developing an ASP.NET MVC application that reads and writes data from a SQL
Server database. You need to maintain data integrity in all situations that use transactions.
A.
ReadUncommitted
B.
Repeatable
C.
Serializable
D.
ReadCommitted
You need to maintain data integrity in all situations that use transactions.
You are developing an ASP.NET MVC application that reads and writes data from a SQL
Server database. You need to maintain data integrity in all situations that use transactions.
Why not Serializable? ReadCommitted allows data to be changed before the end of a transaction.
You are right. The same question in the previous set has the answer as “Serializable”.
serializable: permite manejar la integridad de los datos debido a que este permite detener las demas transaciones por medio de un rango de estas mientras se este usando un select impediendo que se ejecute alguna transacion que incluya dentro de este rango
https://technet.microsoft.com/en-us/library/ms189122(v=sql.105).aspx
The above TechNet article indicates that Serializable is the highest isolation level which ensures data integrity, but at a cost to performance and concurrency.
Another nice reference regarding the code for transactions.
https://msdn.microsoft.com/en-us/data/dn456843.aspx
Answer is C > SERIALIZABLE
Statements cannot read data that has been modified but not yet committed by other transactions.
No other transactions can modify data that has been read by the current transaction until the current transaction completes.
Other transactions cannot insert new rows with key values that would fall in the range of keys read by any statements in the current transaction until the current transaction completes.
https://msdn.microsoft.com/en-us/library/ms173763.aspx