You use Microsoft SQL Server 2012 to write code fora transaction that contains several statements. There is
high contention between readers and writers on several tables used by your transaction. You need to minimize
the use of the tempdb space. You also need to prevent reading queries from blocking writing queries. Which
isolation level should you use?
A.
SERIALIZABLE
B.
SNAPSHOT
C.
READ COMMITTED SNAPSHOT
D.
REPEATABLE READ
Explanation:
Reference: http://msdn.microsoft.com/en-us/library/ms173763.aspx
It has to be B. READ COMMITTED SNAPSHOT is not a isolation level for a transaction but rather a database option.
0
0
riemi is right. READ_COMMITTED_SNAPSHOT is a database option – not an isolation level
0
0
I agree with riemi and dennis but
https://msdn.microsoft.com/en-us/library/ms173763.aspx
Read committed snapshot listed as an isolation level next to the statement
FILESTREAM-enabled databases support the following transaction isolation levels.
0
0
Read committed isolation is recommended over snapshot because it consumes less tempdb space than snapshot isolation which is part of the requirements
0
0
To solve this problem
1. “There is high contention between readers and writers”
SNAPSHOT and RED COMMITTED SNAPSHOT will not apply share locks so minimize the the contention
https://msdn.microsoft.com/en-us/library/ms173763.aspx
2. “need to minimize the use of the tempdb space”
RED COMMITTED SNAPSHOT uses less tempdb space
https://msdn.microsoft.com/en-us/library/ms378149(v=sql.110).aspx
So the answer is RED COMMITTED SNAPSHOT
0
0
Usually posts some incredibly interesting stuff like this. If you are new to this site.
0
0
Every as soon as in a although we choose blogs that we study. Listed beneath would be the most recent web sites that we pick
0
0
here are some hyperlinks to web pages that we link to simply because we assume they may be worth visiting
0
0
although websites we backlink to below are considerably not related to ours, we really feel they’re truly really worth a go by way of, so have a look
0
0
usually posts some extremely fascinating stuff like this. If you are new to this site
0
0
Sites of interest we’ve a link to
0
0
Here is a good Blog You may Locate Fascinating that we Encourage You
0
0
very handful of internet sites that take place to become detailed beneath, from our point of view are undoubtedly nicely really worth checking out
0
0
Here are a number of the web pages we suggest for our visitors
0
0
The details mentioned inside the article are a number of the top available
0
0
the time to study or check out the material or web pages we have linked to below the
0
0
Sites of interest we’ve a link to
0
0
Sites of interest we’ve a link to
0
0
The answer is B.
1. READ_COMMITTED_SNAPSHOT isn’t a transaction isolation level. It is a database option that changes the behavior of the default isolation level READ_COMMITTED. This was done in order to make it easier for applications to work with snapshot isolation without having to change application code.
2. READ_COMMITTED_SNAPSHOT changes the behavior for ALL QUERIES in the database and would carry greater performance impact on the tempdb database than simply using SNAPSHOT_ISOLATION for this single transaction.
0
0