Index scan (IXSCAN) with matching predicates.
使用匹配谓词的索引扫描(IXSCAN)。
This query plan shows an index scan using our functional index.
该查询计划显示索引扫描使用了函数索引。
When scanning an MDC table, block locking could be deferred for an index scan.
当扫描一个mdc表时，对于索引扫描，块锁可以推迟。
This guideline specifies that a single XML index scan be used to access the given table.
该准则指定一个单一的xml索引扫描，将用于访问给定的表。
The outer table can be accessed by an index scan or by a table scan, depending on the table.
通过索引扫描还是表扫描来访问外部表则取决于该表。
An index scan is typically shown in Query Tuner as a group of four nodes in the access path graph.
在访问路径图中，一个索引扫描通常作为一组四个节点显示在QueryTuner上。
A new feature of the query optimizer supports a new type of index scan, called an index self-join path.
查询优化器的一项新特性支持一种新的索引扫描，即索引自连接路径。
Thus, all indexed strings with the same hash code are returned from the index scan as possible candidates.
因此，索引扫描返回所有具有相同hash码的已索引的字符串，作为可能的候选者。
There is a nested loop join (NLJOIN, step 4) of the insert (step 5) to an index scan (IXSCAN, step 7).
其中有一个insert（步骤5）与索引扫描（步骤7）之间的嵌套循环连接（NLJOIN，步骤4 ）。
Gather counts for base accesses (an index scan or a table scan of a table) that are not dependent on a join.
收集不依赖于连接(JOIN)的基本访问(表的索引扫描和表扫描)的计数。
An index scan can be non-matching, which means that there are no restrictions in the scan of the underlying index.
索引扫描可以是非匹配的，这意味着在基础索引的扫描上没有限制。
Without an index sarg, an index scan will use the index to access the data, but will return every key in the index.
没有索引sarg时，索引扫描将使用索引访问数据，但是会返回索引中的所有键。
Here we are using the two indexes, and we have the same predicate, this time on the index scan numbered 3 in the plan.
在这里我们使用了两个索引，并且有同样的谓词，这一次针对计划中编号为3的索引扫描。
The optimizer normally chooses a table scan if no appropriate index has been created or if an index scan would be more costly.
如果没有创建合适的索引，或者如果索引扫描的成本更高一些，优化器通常就选择表扫描。
For example, improperly coded predicates might prevent the optimizer from using an index scan even when the index is available.
例如，使用不正确的谓词会妨碍优化器使用索引扫描，即使在索引可用的情况下。
Access plan directives that force the optimizer to use the designated access method for data retrieval, either sequential scan or index scan.
访问计划指示，强制优化器使用指定的访问方法进行数据检索，要么是连续扫描，要么是索引扫描。
This is a sargable predicate, but not an index-sargable predicate (that is, it cannot be applied as a start/stop key on the index scan).
这是一个sargable谓词，而不是一个索引sargable 谓词（即，它不能作为索引扫描的开始/停止键）。
Like the existing relational index scan operator for relational indexes (IXSCAN), the XISCAN operator performs lookups or scans on XML indexes.
类似于现有的用于关系索引的关系索引扫描操作符(IXSCAN)，XISCAN操作符在xml索引上执行查找或扫描。
In the previous section you learned about one type of access method, index scan (IXSCAN), and one type of join method, nested loop join (NLJOIN).
在之前的部分您已经了解了一种类型的访问方法，即索引扫描(IXSCAN)，和一种类型的联接方法，即嵌套循环联接(NLJOIN)。
For multiple index push-downs, multi-index scan is used to combine RIDs from different index scans, then skip-scan on the fact table is performed.
对于多索引下推，多索引扫描用于组合来自不同索引扫描的RID，然后就可以执行对事实表的跳跃式扫描了。
An index scan might be more costly when the table is small and the index-clustering ratio is low, or the query requires most of the table rows.
当表十分小且索引集群率(index -clustering ratio)十分低，或查询需要很多表行时，索引扫描的成本可能更高。
As was mentioned in the previous article, for single table access, there are two types of access methods: table space scan (TBSCAN) and index scan (IXSCAN).
在第1部分中提到过，有两种类型访问方法：表空间扫描(TBSCAN)和索引扫描(IXSCAN)。
For instance, the purchaseOrders table is partitioned by po_date and has a local index on po_customer, the query below will need a sort after the index scan.
例如，表purchaseorders通过po_date进行了分区，并具有本地索引po_customer，以下查询在完成索引扫描后还需要进行排序。
Sorting is required when no index satisfies the requested ordering of fetched rows, or the optimizer determines that a sort is less expensive than an index scan.
如果没有索引满足所取的行的要求顺序，或者优化器断定排序的代价低于索引扫描，那么就需要进行排序。
To illustrate this, compare it to the predicate that is applied to the index scan numbered 5 in the plan, which is on the one and only column of the index on the child table.
为了展示这一点，将它与计划中第5号索引扫描上使用的谓词相比较，它针对子表中惟一的索引列。
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.
通常情况下，在基础索引提供好处(如唯一索引访问、避免排序或一些类似的好处)时，可通过优化器选择非匹配索引扫描。
Furthermore, deleted rows are skipped unconditionally on table scan access while deleted keys are not skipped for type-2 index scans unless the registry variable DB2_SKIPDELETED is also set.
而且，虽然在type - 2索引扫描中，被删除的行不会被跳过，但是除非同时设置了注册表变量db2_skipdeleted，否则在表扫描访问中，被删除的行将被无条件跳过。
An index only scan is an index access that is not followed by a table access because the index itself contains all the requested data.
仅扫描索引是未包含表访问的索引访问，因为索引本身包含了所有被请求的数据。
If DB2 used a single index range scan from 20 to 30, it would miss this document and return an incomplete query result.
如果DB 2在20到30之间使用单个索引范围扫描，则会错过该文档，并返回不完全的查询结果。
During the foreign key enforcement, the server USES the sequential scan, instead of foreign key index.
在外键加强过程中，服务器使用顺序扫描，而不是外键索引。
应用推荐