The DB2 optimizer is not all-knowing.
DB 2优化器不是无所不知的。
The DB2 optimizer is not all-controlling.
DB 2优化器不能控制一切。
Index advisor and optimizer enhancements.
Index顾问程序和优化器增强。
The DB2 optimizer creates the access plans.
DB2优化器可以创建访问计划。
Runstat - collects statistics used by optimizer
Runstat ——收集优化器所使用的统计数据
Storing and applying external optimizer directives.
存储和应用外部优化器指令。
By default, the optimizer considers this type of scan.
默认情况下，优化器考虑这种类型的扫描。
The DB2 optimizer is comprehensive and quite powerful.
DB 2优化器很全面，而且很强大。
After QRW optimization, the DB2 optimizer gets involved.
在QRW优化之后，DB 2优化器就会介入。
The DB2 optimizer is a highly sophisticated cost-based optimizer.
DB 2优化器是一款高度复杂的基于成本的优化器。
You can create, save, and reuse external optimizer directives.
可以创建、保存和重用外部优化器指令。
The optimizer has many types of strategies for optimizing SQL.
优化器有许多类型的优化SQL的策略。
REOPTimizing bind options to improve optimizer plan selection.
重新优化绑定选项以改善优化器计划选择。
To enable the opcode optimizer, add — enable-xcache-optimizer.
要启用操作码优化，添加——enable - xcache - optimizer。
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 optimizer USES all applicable XML indexes in the XANDOR plan.
优化器在XAND OR计划中使用所有合适的xml索引。
The RDBMS optimizer accomplishes this substitution in an automatic way.
RDBMS优化器以自动方式来完成这种替代。
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 query optimizer does not recalculate the profile for tables automatically.
查询优化器不会自动重新计算表的配置文件。
Text search is integrated into SQL and optimized by the DB2 optimizer for run time.
文本搜索集成到SQL 中，DB2优化器在运行时会对它进行优化。
Optimal database performance requires the database optimizer to do its job well.
最优数据库性能还需要数据库优化器很好地发挥作用。
The optimizer chooses between the two access methods using a cost-based analysis.
优化器将通过基于成本的分析来在这两个访问方法之间进行选择。
Join order directives that force optimizer to join tables in the designated order.
连接次序指示，强制优化器按照指定次序连接表。
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.
下面是优化器为表空间所使用的重要信息。
DB2's optimizer is the component that accomplishes this physical data independence.
DB2的优化器是完成该物理数据独立性的组件。
应用推荐