我们只选择索引，因为这正是我们的兴趣所在。
We select only Indexes as that is what we are interested in.
如果将其值设置为0，那么当存在合适的索引时，优化器就选择索引扫描而非表扫描，甚至不考虑估算成本。
If the value is set to 0, then the optimizer chooses index scans over table scans if appropriate indexes exist, without even considering the estimated costs.
这个例子演示了如何使用函数索引选择具有某些特征的图像。
This example demonstrates how functional indexes can be used to select images with certain characteristics.
使用事件处理程序的索引来从全局输入列表中选择输入值。
Use the event handler’s index to select the input out of the global input list.
这意味着可以使用它们来索引频繁在谓词和连接中使用的所选择的元素和属性。
That means you can use them to index selected elements and attributes that are frequently used in predicates and joins.
基本上，它会权衡使用索引来遍历选择的行或者对表进行扫描这两种方式。
Basically, it's weighing the choice of using the index to walk through the selected rows or doing a table scan.
现在将用优化器根据实际和虚拟索引选择的访问计划来填充解释表。
This now populates the explain tables with the access plan chosen by the optimizer based on real and virtual indexes.
DB 2 9.5优化器使用两种类型的索引来优化查询，并帮助选择最佳的查询执行计划。
The DB2 9.5 optimizer USES both type of indexes to optimize the queries and help selecting the best plan for query execution.
WHERE子句中的字段决定了数据库将选择的索引。
The columns in the WHERE clause decide what index the database will select.
同样，用于根据索引中的选择列出货品的查询也将发生变化以包括新条件。
Similarly, queries used to list items based on a selection in the index would also change to take in the new criteria.
通过这样做，您可以选择创建能带给您最佳性能的索引。
By doing so, you can choose to create the indexes that can help give you the performance that you want.
索引的顺序由优化器选择。
表1最右侧的两列表示两个可选择的索引定义，表中各行展示了谓词可以(+)或不可以(-)由这两个索引进行计算。
The two rightmost columns in table 1 represent two alternative index definitions, and the rows in the table show which of the predicates can (+) or cannot (-) be evaluated by either of the indexes.
对于分区索引，建议选择不大可能改变的键列。
For partitioning indexes, it is recommended that you choose key columns that are unlikely to be changed.
使用事件处理程序的索引来在结果变量列表中选择恰当的Slot。
Use the event handler's index to select the appropriate slot in the list of the result variable.
请确保使用合适的索引，从而在选择和连接(join)表时，将必须在内部访存的行数减到最少。
Make sure appropriate indexes are used to minimize the rows that have to be fetched internally when selecting and joining tables.
这个方法使用当前状态和事件类型作为关联数组的索引，从actionTransitionFunctions表中选择要调用的函数。
The method does select a function to call from the actionTransitionFunctions table using the current state and event type as associative array indexes.
这个号码将用于作为分区映射的一个索引，以选择那一行所在的数据库分区。
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.
我们选择的索引位于(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.
然而在缺乏数据分布信息的情况下，优化器将基于表索引计算不同类型筛选器的选择性。
However, in the absence of data distribution information, the optimizer will calculate selectivity for filters of different types based on table indexes.
顺便说一句，一旦选择其他的搜索引擎，火狐会一直记住，知道你再次把它换成其他的。
By the way, once you do go to another search engine, Firefox stays with it until you change again.
对于多个索引，每个索引都针对特定目的而定制，您可以选择最适当的索引来优化搜索结果。
With multiple indexes, each tuned for a specific purpose, you can choose the most appropriate index to optimize search results.
首先来分析一下，在没有分布统计信息，而只有cars表的基本统计信息及其索引的情况下，优化器选择的访问计划是怎样的。
First analyze the access plan that the optimizer chooses when no distribution statistics are available, which is only basic statistics for the table CARS, and that its indexes exist.
这意味着，DB 2从重新构建和增量索引维护两种方法中选择最合适的方法。
This means that DB2 chooses either the rebuild or incremental index maintain approach, whichever is the best fit.
添加关键词搜索，选择管理搜索引擎…在搜索引擎的下拉菜单上，打开搜索引擎管理器，选择一个，点击编辑键…然后输入定义的关键词。
To add keyword search select Manage Search Engines… in the search engines menu to open the Search Engines Manager, select a search engine, press Edit Keyword… and enter a few characters to define one.
这些建议涉及了数据库模式、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.
如果没有创建合适的索引，或者如果索引扫描的成本更高一些，优化器通常就选择表扫描。
The optimizer normally chooses a table scan if no appropriate index has been created or if an index scan would be more costly.
选择想要索引的XML文档的文件夹。
选择想要索引的XML文档的文件夹。
应用推荐