There’s a new property called “NoLock” added to the QueryExpression class for Microsoft Dynamics CRM 2011. I found this researching a locking issue on the database we were having for a client. According to the Microsoft CRM 2011 SDK:
“The benefit of setting NoLock to true is that it allows you to keep the system from issuing locks against the entities in your queries; this increases concurrency and performance because the database engine does not have to maintain the shared locks involved. The downside is that, because no locks are issued against the records being read, some “dirty” or uncommitted data could potentially be read. A “dirty” read is one in which the data being read is involved in a transaction from another connection. If that transaction rolls back its work, the data read from the query using NoLock will have read uncommitted data. This type of read makes…
View original post 35 more words
3 thoughts on “”
We have to same property in fetch xml as well
Thanks Nishant! And Varun, you are correct, it’s present in the fetch xml as well. Thanks guys!
Thank you Danny for your insightful post and your prompt reply 🙂