ADO.NET和大多数OR / M框架的默认事务隔离级别。

This is the default transaction isolation level for ADO.NET and most OR/M frameworks. Chances are this is in fact coming for your code, you just don't know it.

我认为无论如何这都是一个错误的问题-真正的问题是，为什么这条相当普遍的TSQL指令导致您的数据库CPU峰值？

I think this is the wrong question to ask anyways - the real question is, why is this rather common TSQL instruction causing your database CPU to spike?