sql,server,如何查看执行计划.docVIP

sql,server,如何查看执行计划 ：执行 计划 查看 sql server sql server索引 sql server分区 存储过程执行计划 篇一：SQLServer查询执行计划分析 看懂执行计划 例子1 以AdventureWorks的DatabaseLog查询为例： SELECT * FROM [AdventureWorks2008R2].[dbo].[DatabaseLog] ? Cached plan size – how much memory the plan generated by this query will take up in stored procedure cache. This is a useful number when investigating cache performance issues because you#39;ll be able to see which plans are taking up more memory. ? Estimated Operator Cost – we#39;ve already seen this as the percentage cost in Figure 1. ? Estimated Subtree Cost ?tells us the accumulated optimizer cost assigned to this step and all previous steps, but remember to read from right to left. This number is meaningless in the real world, but is a mathematical evaluation used by the query optimizer to determine the cost of the operator in question; it represents the amount of time that the optimizer thinks this operator will take. ? Estimated number of rows ?calculated based on the statistics available to the optimizer for the table or index in question. The logical operators are the results of the optimizer#39;s calculations for what should happen when the query executes. The physical operators represent what actually occurred. The logical and physical operators are usually the same, but not always The Subtree is simply the section of the execution tree that we have looked at so far, working right to left again, and top to bottom. All estimations are based on the statistics available on the columns and indexes in any table. The I/O Cost and CPU cost are not actual operators, but rather the cost numbers assigned by the Query Optimizer during its calculations. These numbers are useful when determining whether most of the cost is I/O-based (as in this case), or if we#39;re putting a load on the CPU. A bigger number means more processing in this area. You#39;ll note that, in this case, the operator cost and the subtree cost are the same, since the t