查询分析器 VS. 查询分析器读取、写入和持续时间差异
我使用的是 MS Sql Server 2000，对于许多查询，当我在查询分析器中运行查询时，打开统计信息，统计信息选项卡中报告的数字与查询分析器中显示的值非常不同。 当探查器和分析器同时运行时，某些查询在分析器中报告 200 个读取，而探查器报告查询执行了 14000 个读取。 根据查询性能，在我看来，Profiler 是正确的。 然而，为什么两者之间会有这么大的差距呢？ 还有其他人有发生同样事情的经历吗？
I'm using MS Sql Server 2000, and for many queries when I run a query in Query Analyzer, with the statistics turned on, the numbers reported in the statistics tab are extremely different from the values shown in the Query Profiler. When the profiler and the analyzer are running at the same time, some queries report 200 reads in Analyzer, while the Profiler reports that the query preforms 14000 reads. Based on query performance, it appears to me that the Profiler is right. However, why is there such a large discrepancy between the two? Does anybody else have experience with the same thing occuring?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这两个实用程序执行不同的操作：
SQL Profiler 监视正在发生的情况并对其进行报告。
查询分析器查看 SQL 代码并弄清楚如何运行它。
查询分析器使用统计信息来确定它将要执行的操作，但结果只是一个行动计划，即使显示了统计信息。
SQL Profiler 会事后报告所发生的情况 - 它更准确，但具有追溯性。
如果您发现查询分析器变得非常不准确，请尝试更新统计信息。
These two utilities do different things:
SQL Profiler watches what's happening and reports on it.
Query Analyzer looks at the SQL code and figures out how to run it.
Query Analyzer uses statistics to figure out what it's going to do, but the results are an action plan, even if statistics are shown.
SQL Profiler reports afterwards on what happened - it's more accurate, but is retroactive.
Try updating your statistics if you find that Query Analyzer becomes very inaccurate.