暂时无法在支持网站上提交享有定期维护的产品表单。 如果您需要我们立即提供帮助,请与技术支持部门联系。 对于由此给您带来的不便,我们深表歉意。
获得即时帮助
完成注册
登录
请求定价
联系销售人员
您已选择一个产品捆绑包。 您能否选择单个产品以便我们更好地满足您的请求。 *
技术支持工程师目前正忙,无法回应您的消息。 如果需要即时服务,请通过我们的服务请求表提交请求。
以下文章可根据您的描述解决您的问题。
Time spent by the various sessions either consuming or waiting for CPU cycles. This reading is an aggregation of CPU Usage and CPU Wait, which are both taken directly from the operating system (rather than MSSQL wait states).
Number of seconds a page will stay in the buffer pool without references. Low values of this metric require the buffer pool to frequently flush the page to the physical disk, thereby possibly indicating a memory issue. Such an issue should be investigated to see if it results from lack of physical memory, inefficient queries and so on.
Number of page splits taking place.
Page splitting occurs when an index or data page becomes full and then is split between the existing page and a newly allocated page.
Excess page splitting can lead to I/O performance issues, indicating a need to rebuild indexes and/or increase the indexes’ fill factor.
The time spent by the various processes coordinating parallel query threads and exchanging data.
If the server on which SQL Server is running has multiple CPU cores, SQL Server can run a single query in parallel, using multiple threads. In addition to running user queries on multiple processors, SQL Server can also use multiple threads to build indexes. Typically, queries that make heavy use of CPU cycles are good candidates for parallel execution. For example, a query joining several large tables and sorting the output before returning it to the user is likely to benefit from a parallel execution plan.
您可以在附属支持站点上查找适用于戴尔*产品*的在线支持帮助。单击“继续”,转至适用于*产品*的正确支持内容和帮助。
The document was helpful.
选择评级
I easily found the information I needed.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center
Quest Software门户不再支持IE 8、9和10,建议将您的浏览器升级到最新版本的Internet Explorer或Chrome。
要升级到IE 11,请单击此处
要升级到Chrome,请单击此处
如果继续使用IE 8、9和10,您将无法充分利用我们所有出色的自助服务功能。