本文专注于索引匹配，而不是优化器的索引选择。
In this article, the focus is on index matching rather than the optimizer's index selection.
那些统计数据用于协助索引选择，而不是谓词重排。
Those statistics are used to aid in index selection, not for predicate rearrangement.
这本书有好的索引选择叁考书目和组织。
This book has good indexes to selected bibliographies and organizations.
这个例子演示了如何使用函数索引选择具有某些特征的图像。
This example demonstrates how functional indexes can be used to select images with certain characteristics.
现在将用优化器根据实际和虚拟索引选择的访问计划来填充解释表。
This now populates the explain tables with the access plan chosen by the optimizer based on real and virtual indexes.
我们只选择索引，因为这正是我们的兴趣所在。
We select only Indexes as that is what we are interested in.
这个号码将用于作为分区映射的一个索引，以选择那一行所在的数据库分区。
That number is used as an index into the partitioning map to select the database partition for that row.
一旦理解了自己的选择，就可以通过调整OPTCOMPIND参数，或者通过添加查询指示或索引，来影响优化器，从而选择最佳的查询执行计划。
Once you understand your options, you can influence the optimizer to select the best query execution plan, either by adjusting the OPTCOMPIND parameter or by adding query directives or indexes.
使用事件处理程序的索引来从全局输入列表中选择输入值。
Use the event handler’s index to select the input out of the global input list.
如果连接列上不存在索引，那么优化器将选择动态哈希连接。
The optimizer will choose dynamic hash join if none of the joined columns has index.
这些建议涉及了数据库模式、XML与关系存储之间的选择、索引的定义以及带有分区和集群选项的物理数据组织。
These recommendations address the database schema, the choice between XML and relational storage, definition of indexes, and physical data organization with partitioning and clustering options.
选择想要索引的XML文档的文件夹。
基本上，它会权衡使用索引来遍历选择的行或者对表进行扫描这两种方式。
Basically, it's weighing the choice of using the index to walk through the selected rows or doing a table scan.
它高效，因为索引适合于最佳访问路径的选择。
It is efficient, as the indexes qualify for the choice of excellent access paths.
WHERE子句中的字段决定了数据库将选择的索引。
The columns in the WHERE clause decide what index the database will select.
我们选择的索引位于(COLA,COLB,COLC)上，因此那些谓词—上面的示例中的前三行—将以那个顺序应用。
Our chosen index is on (COLA, COLB, COLC), so those predicates-the first three lines in the preceding example-will be applied in that order.
同样，用于根据索引中的选择列出货品的查询也将发生变化以包括新条件。
Similarly, queries used to list items based on a selection in the index would also change to take in the new criteria.
索引设计对访问路径选择至关重要。
Index design has a critical impact on access path selection.
进入控制面板，选择索引选项。
您可以现在或者以后再选择运行初始索引。
You may choose to run the initial index, now or at a later date.
通常情况下，在基础索引提供好处(如唯一索引访问、避免排序或一些类似的好处)时，可通过优化器选择非匹配索引扫描。
Typically, a non-matching index scan is chosen by the optimizer when the underlying index provides benefits such as index-only access, avoids sort, or some similar benefit.
这个值越低，优化器就越有可能选择扫描网格索引。
The lower this value is the more likely the optimizer will choose to scan the grid index.
为了便于讨论，我们选择的索引是一个三列索引，名为IX1，在(COLA,COLB,COLC)上创建。
For the purposes of discussion, our chosen index is a three-column index called IX1 created on (COLA, COLB, COLC).
索引的顺序由优化器选择。
对于分区索引，建议选择不大可能改变的键列。
For partitioning indexes, it is recommended that you choose key columns that are unlikely to be changed.
请确保使用合适的索引，从而在选择和连接(join)表时，将必须在内部访存的行数减到最少。
Make sure appropriate indexes are used to minimize the rows that have to be fetched internally when selecting and joining tables.
使用索引，但要小心选择。
从restdoc索引中选择process资源。
另一个原则是迫使优化器选择索引“或”操作来访问employee表。
A guideline to force the optimizer to choose the index oring operation to access the EMPLOYEE table.
优化器极可能会选择使用 order_date 上的索引，而不是选择使用state 上的索引。
The optimizer will most likely choose to use the index on order_date rather than the index on state.
应用推荐