You are a database administrator for AIOTestKing.com. Users report that a SQL Server 2005 application is performing slowly. You check the SQL Server error log and discover that the server frequently runs out of memory to manage locks. The application designer informs you that dirty reads are acceptable. You need to resolve the problem indicated by the error log. What should you do?
A.
Implement the Read Uncommitted isolation level.
B.
Execute the sp_locks stored procedure.
C.
Increase the maximum number of worker threads.
D.
Configure the SQL Server max server memory setting to be a lower value.
Explanation:
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.