title: Use of TransactionScope with read uncommitted - is with (nolock) in SQL necessary?
body: <p>I am using FluentNHibernate, and I have a list of records, mapped to an SQL Server 2008 view. Dirty reads are OK with me, not locking the tables is a priority.</p>
  
  <p>The SQL Query inside the view, does not have any with (nolock), however, I am using the following approach...</p>
  
  <pre>
  using (var txScope = new TransactionScope(TransactionScopeOption.Suppress, new TransactionOptions() { IsolationLevel = System.Transactions.IsolationLevel.ReadUncommitted }))
  {
     ... The reading of records from the view is done here, through Fluent NHibernate...
  }
  
  </pre>
  
  <p>Does setting the isolation level at application layer to read uncommitted, apply with (nolock) to the queries which are generated within that context?</p>