What should you do?

You are the database administrator for AIOTestKing.com. The company uses a SQL Server 2005 database to track online sales. Employees who run the In-Stock report experience slow performance. This performance problem is caused by the contention between the In-Stock report and high volume of data entry to the tables that are accessed in this report. The company wants the In-Stock report returned immediately even though other employees might be changing the data within their data-entry transactions. Any changes made in other transactions while the report is running must be visible to the employees who are running the In-Stock report. You need to design a solution to achieve this goal.
What should you do?

A.
Change the transaction isolation level for the report transaction to snapshot.

B.
Change the transaction isolation level for the report transaction to serializable.

C.
Change the transaction isolation level for the report transaction to Read Uncommitted.

D.
Configure the database to enable the Read Committed snapshot option.

Explanation:
READ UNCOMMITTED Specifies that statements can read rows that have been modified by other transactions but not yet committed. Transactions running at the READ UNCOMMITTED level do not issue shared locks to prevent other transactions from modifying data read by the current transaction. READ UNCOMMITTED transactions are also not blocked by exclusive locks that would prevent the current transaction from reading rows that have been modified but not committed by other transactions. When this option is set, it is possible to read uncommitted modifications, which are called dirty reads. Values in the data can be changed and rows can appear or disappear in the data set before the end of the transaction. This option has the same effect as setting NOLOCK on all tables in all SELECT statements in a transaction. This is the least restrictive of the isolation levels.