The optimizer is the heart and soul of DB2.
优化器是 DB2的心脏和灵魂。
When the optimizer can choose a star join plan.
优化器何时可以选择星型连接计划。
The order of indexes is chosen by the optimizer.
索引的顺序由优化器选择。
By default, the optimizer considers this type of scan.
默认情况下，优化器考虑这种类型的扫描。
The choice of the access method is left to the optimizer.
选择访问方法的任务交给优化器来完成。
The optimizer has many types of strategies for optimizing SQL.
优化器有许多类型的优化SQL的策略。
The following explains why the optimizer would add a SORT node.
以下解释了为什么优化器将添加SORT节点。
The optimizer will add more indexes to the IXAND based on cost.
优化器将根据成本向IXAND添加更多索引。
The total number of rows, estimated by the optimizer, is 2.176.
优化器估计的总行数是 2.176。
The optimizer USES all applicable XML indexes in the XANDOR plan.
优化器在XAND OR计划中使用所有合适的xml索引。
Another way to influence the optimizer is to use query directives.
影响优化器的另一种方式就是使用查询命令。
Multiple index scans in the optimizer are another big win for OLTP.
优化器中的多索引扫描是OLTP的另一大赢点。
The sort heap size is used by the optimizer in determining access paths.
优化器用排序堆大小来确定存取路径。
The optimizer will return the best plan using a cost-based decision.
优化器将通过基于成本的决策返回最佳计划。
The optimizer can decide to not use an index even if it could be used.
优化器可以决定不使用索引，即使该索引是可以使用的。
For example, the optimizer must determine whether indexes should be used.
例如，优化器必须确定是否应使用索引。
A value of -1 means that the optimizer determines the degree of asynchrony.
若该选项值为- 1，则意味着优化器自行决定异步程度。
The optimizer performs complex calculations based on a host of information.
优化器根据许多信息执行复杂的计算。
The optimizer will decide whether an index can be used to evaluate a filter.
优化器将决定是否可以使用索引来评估筛选器。
The optimizer may add more indexes to the IXAND plan in a cost-based fashion.
优化器可能会以一种基于成本的方式将更多索引加入到 IXAND计划中。
The optimizer chooses between the two access methods using a cost-based analysis.
优化器将通过基于成本的分析来在这两个访问方法之间进行选择。
The estimated costs are cost units that the optimizer uses to compare query plans.
估算成本是优化器用来比较查询计划的成本单元。
The optimizer picks additional indexes for the IXAND plan in a cost-based fashion.
优化器将以一种基于成本的方式为IXAND计划挑选额外的索引。
The important information used by the optimizer for a tablespace is the following.
下面是优化器为表空间所使用的重要信息。
The optimizer will compare the cost of each method to determine the best one to use.
优化器将比较每种方法的成本，确定使用最好的一种。
The optimizer will choose dynamic hash join if none of the joined columns has index.
如果连接列上不存在索引，那么优化器将选择动态哈希连接。
Therefore the optimizer is aware of the different frequencies of the available models.
因此，优化器清楚各种已有型号出现的不同频率。
Note: Here is a query for which the optimizer cannot consider using the functional index.
注意：优化器不会对下面这个查询使用函数索引。
The access guideline (any access request) allows the optimizer to choose the access method.
ACCESS准则(任何访问请求)允许优化器选择方法。
The access guideline (any access request) allows the optimizer to choose the access method.
ACCESS准则(任何访问请求)允许优化器选择方法。
应用推荐