I am using Entity Framework 6 in an MVC 5 project. As you\'re aware of, SELECT
queries in SQL Server perform faster and more efficient if we use WITH (NOL
First of all... You should NEVER EVER use NOLOCK for each and every SQL Statement. It could compromise the integrity of your data.
It’s like any other query hint a mechanism you should only use when you do something out of the ordinary.
There is no way to tell the EF Provider to render the NoLock hint. If you really need to read uncommitted data you have the following option.
Write your own EntityFramework Provider.
Use a Command Interceptor to modify the statement before it is executed. http://msdn.microsoft.com/en-us/data/dn469464.aspx
Use a TransactionScope with IsolationLevel.ReadUncommited.
I know you said you do not want to use Transactions but it's the only out-of-the box way to read uncommitted data. Also it does not produce much overhead as each statement in SQL Server “implicitly” runs in a transaction.
using (new TransactionScope(
TransactionScopeOption.Required,
new TransactionOptions
{
IsolationLevel = IsolationLevel.ReadUncommitted
}))
{
using (var db = new MyDbContext()) {
// query
}
}
EDIT: It's important to note also that NOLOCK for Updates and Deletes (selects remain intact) has been Deprecated by Microsoft as of SQL Server 2016 and and will be removed in 'a' future release.
https://docs.microsoft.com/en-us/sql/database-engine/deprecated-database-engine-features-in-sql-server-2016?view=sql-server-2017