SQL Server 2005中的活动监视器问题 [英] Activity Monitor Problems in SQL Server 2005

查看:273
本文介绍了SQL Server 2005中的活动监视器问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在查看SQL Server 2005的活动监视器,我们有一些进程占用大量CPU。当我查看要运行的内容时,会得到:

I am looking at the Activty Monitor for SQL Server 2005 and we have some processes that are taking up large amounts of the CPU. When I look at what is trying to be run I get:

set transaction isolation level  read committed 

此代码不是来自我们的任何应用程序。

This code is not coming from any of our applications.

什么是

应该做什么?

推荐答案

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?

这篇关于SQL Server 2005中的活动监视器问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆