Which isolation level should you identify?

You plan to deploy two stored procedures name USP_1 and USP_2 that read data from a database.
Your company identifies the following requirements for each stored procedure:
USP_1 cannot allow dirty reads.
USP_2 must place range locks on the data to ensure read consistency.
You need to identify which isolation level you must set for each stored procedure. The solution must minimize
the number of locks.
Which isolation level should you identify?
To answer, drag the appropriate isolation level to the correct stored procedure in the answer area. (Answerchoices may be used once, more than once, or not at all.)
Select and Place:

You plan to deploy two stored procedures name USP_1 and USP_2 that read data from a database.
Your company identifies the following requirements for each stored procedure:
USP_1 cannot allow dirty reads.
USP_2 must place range locks on the data to ensure read consistency.
You need to identify which isolation level you must set for each stored procedure. The solution must minimize
the number of locks.
Which isolation level should you identify?
To answer, drag the appropriate isolation level to the correct stored procedure in the answer area. (Answerchoices may be used once, more than once, or not at all.)
Select and Place:

Answer:

Explanation:
* read committed
READ COMMITTED
Specifies that shared locks are held while the data is being read to avoid dirty reads, but the data can be
changed before the end of the transaction, resulting in nonrepeatable reads or phantom data. This option is the
SQL Server default.
* SERIALIZABLE
Places a range lock on the data set, preventing other users from updating or inserting rows into the data set
until the transaction is complete. This is the most restrictive of the four isolation levels. Because concurrency is
lower, use this option only when necessary. This option has the same effect as setting HOLDLOCK on all tables
in all SELECT statements in a transaction.
https://msdn.microsoft.com/en-us/library/tcbchxcb(v=vs.110).aspx



Leave a Reply 0

Your email address will not be published. Required fields are marked *