Queries that use NOLOCK aren't guaranteed to return correct results or technically, return any results at all.
使用了NOLOCK的查询并不保证能返回正确地结果，而且从技术上讲，它可能会返回任意结果。
There are also arguments about using NOLOCK at all and where the NOLOCK should live when considering deployment.
也有一些争论是关于NOLOCK选项本身，以及是否应该在部署时使用NOLOCK选项。
However, with NOLOCK (even though "everyone" has used it at some point or another) is generally considered a last resort.
然而，使用NOLOCK(即使“每个人”多多少少都用过这个方法)通常是最后一个可以依靠的手段。
The problem is actually how to get the SQL generated by LINQ queries to use the NOLOCK hint as SQL developers are accustomed.
这个问题实际是在找出一个办法，使LINQ查询生成的SQL语句能够像SQL开发人员常用的做法那样加上NOLOCK选项。
Of course NOLOCK is only one of many hints used in SQL today and using the techniques above, there is no reason other hints cannot be used the same way.
显然，NOLOCK只是如今SQL中许多选项中的一种。而对于上面提到的技术，也没有证据说明不能用同样的方法使用其它SQL选项。
Of course NOLOCK is only one of many hints used in SQL today and using the techniques above, there is no reason other hints cannot be used the same way.
显然，NOLOCK只是如今SQL中许多选项中的一种。而对于上面提到的技术，也没有证据说明不能用同样的方法使用其它SQL选项。
应用推荐