The optimizer calculates and compares the costs of each join method and selects the best one to use when evaluating query execution plans.
当评估查询执行计划时，优化器计算并比较每种连接方法的成本，然后选择要使用的最佳方法。
The optimizer will compare the cost of each method to determine the best one to use.
优化器将比较每种方法的成本，确定使用最好的一种。
The optimizer would chalk out a query plan before performing the actual join operation itself by making use of the statistical data.
在执行实际的连接操作之前，优化器使用统计数据制定一个查询计划。
You have also examined how the use of parameter markers/host variables may limit the consideration of distribution statistics by the DB2 optimizer.
您还研究了参数标记/主变量的使用会为DB2优化器对分布统计信息的考虑带来怎样的限制。
This set is input to the cost-based optimizer that decides whether to use any of the eligible indexes or not.
将该组索引输入到基于成本的优化器，这个优化器决定是否使用任何合适的索引。
In this scenario, after analysis, it was determined that it will be optimum to use the index I11 to access the table TAB1, but the default behaviour of the optimizer did not, even after tuning.
在这个场景中，经过分析，可以确定使用索引i 11来访问表tab 1是最优的，但是优化器的默认行为不会这么做，即使在调优之后也仍然不会这样做。
The optimizer can use its knowledge of the appliance components to determine the best join order in a complex join.
优化器可以利用其有关设备组件的知识，确定复杂联接操作中的最佳联接顺序。
You can leverage the extended use of multi-column statistics in DB2 9.5 to provide the optimizer more information to better estimate the cardinality in order to choose an optimal query access plan.
您可以利用DB2 9.5 中的多列统计信息的扩展用途来为优化器提供更多的信息，从而使优化器更好地估计基数，选择最佳的查询访问计划。
The optimizer will recognize this index and use the filters on the dimension tables to generate a list of valid combinations of the dimension tables' keys into a temp table.
该优化器将可以识别出这个索引，在维度表上使用过滤器来在一个临时表中生成一个维度表键的有效组合列表。
If the optimizer joins two tables first, the join results could be huge and may use a large amount of system resources such as CPU and memory.
如果优化器首先连接两个表，那么连接结果可能十分庞大，并可能使用大量系统资源，如CPU和内存。
The optimizer ACTS based on statistical data about the number of rows in a table, the use of space by a table or index, and other information.
优化器的操作基于数据表中的行数、数据表或索引使用的空间以及其他信息的相关统计数据。
As the optimizer is not aware of the uneven distribution of the STATE values, it decides to use the index I_TYPE.
由于优化器不知道state值不是均匀分布的，因此它决定使用索引i _ TYPE。
The optimizer won't use an index if the query retrieves a large amount of data from a table.
如果查询从一个表检索大量数据，优化器就不会使用索引。
This feature is really only for use with the assistance of service personnel (it's not the same as the optimizer profiles introduced in DB2 V8.2.2).
该特性实际上只用于帮助服务人员(它不同于db 2V8.2.2中引入的优化器分析)。
The 'DISABLE QUERY OPTIMIZATION' clause may be used to prevent the optimizer from considering use of a particular MQT.
DISABLEQUERYOPTIMIZATION'子句可以用来防止优化器考虑使用特定的MQT。
The query optimization class is used to direct the optimizer to use different degrees of optimization when compiling SQL queries
查询优化类用于在编译SQL 查询时指导优化器使用不同的优化级别。
The db2fopt command tells the optimizer to use the specified value for "buffer pool size," rather than adding up the pages of the buffer pools available.
db 2 fopt命令告诉优化器为“缓冲池大小(Buffer pool size)”使用指定的值，而非将可用缓冲池变量的页面加起来。
To use this service, you would first edit the configuration in the web.xml file of the Optimizer service to point to the root directory of the files you intend to serve through it.
要使用该服务，首先编辑Optimizer服务的web . xml文件中的配置，使其指向您希望对其使用该文件的root目录。
Now the optimizer should have a good starting point. Enable 'use control points of:' for the nadir image, enable Viewpoint optimization for the nadir image, and optimize again.
现在优化器应该有一个良好的起点。启用“使用控制点：'低潮的图像，使图像的角度优化的最低点，和再优化。”
We also propose to use a hybrid version of PSO embedding a local optimizer to enhance the performance.
我们也建议用混合版本的粒子群算法嵌入局部优化，提高了性能。
We also propose to use a hybrid version of PSO embedding a local optimizer to enhance the performance.
我们也建议用混合版本的粒子群算法嵌入局部优化，提高了性能。
应用推荐