This plan USES two XISCANs, one for each predicate and index.
该计划使用两个XISCAN，分别用于每一个谓词和索引。
With this feature, the query optimizer can immediately consider the index when determining an access plan.
有了这个特性，查询优化器可以在决定访问计划时立即考虑索引。
You can define guidelines that influence only a few attributes of an execution plan, such as index specification for a certain table in the query or join order for a pair of tables.
可以定义那些只影响执行计划的某些属性的准则，比如查询中的某个表的索引说明，或者一对表的连接顺序。
This query plan shows the use of a functional index.
该查询计划展示了函数索引的使用。
This query plan shows an index scan using our functional index.
该查询计划显示索引扫描使用了函数索引。
To check if a spatial grid index is actually exploited during query time, you should have a look at the access plan.
为检查在查询时是否真正使用了一个空间网格索引，应该查看一下访问计划。
If only one XML index is available, then DB2 cannot apply this guideline and will instead produce the cheapest alternative plan.
如果只有一个xml索引是可用的，那么DB 2将无法应用这个准则，因而将生成成本最低的替代计划。
If the plan includes a scan of the extended index you will see the EISCAN (highlighted in Figure 3).
如果计划包括对扩展索引的一个扫描，您将发现EISCAN(在图3中高亮显示)。
Access plan directives that force the optimizer to use the designated access method for data retrieval, either sequential scan or index scan.
访问计划指示，强制优化器使用指定的访问方法进行数据检索，要么是连续扫描，要么是索引扫描。
Tuning can include adding extra indexes to yield a more efficient access plan, which makes tables volatile to encourage index usage and avoid table scans if possible.
调优包括添加额外索引来生成一个更高效的访问计划，让表格变幻无常，进而鼓励索引的使用，如果可能的话也可以避免表扫描。
For comparison, Figure 3 illustrates the access plan where I forced the DB2 optimizer to ignore the index by adding the clause SELECTIVITY 1 to the predicate in the where clause.
为了便于比较，图3显示了通过将SELECTIVITY1子句添加到where子句的谓词中，强迫db2优化器忽略索引的访问计划。
When the index name is not specified, optimizer picks the cheapest single XML index access plan.
如果未指定索引名，优化器将选用成本最低的XML 索引访问计划。
If you run the final query from Listing 6, as it is shown above, you should see in the access plan that DB2 decides to use the extended index by the EISCAN operator.
如果运行清单6中最后的查询(如上面所示)，这么在访问计划中应该可以看到，DB 2决定通过EISCAN操作符使用扩展的索引。
Glycemic index diet is a general term for a weight-loss diet that USES the glycemic index to guide your eating plan.
血糖指数瘦身法是那些应用血糖指数指导你的饮食计划的减肥法的统称。
While it may seem that the access plan in Figure 5 is simpler, it comes with a higher estimated execution cost because no index could be exploited to filter out non-qualifying rows.
虽然看上去图5中的访问计划更简单，但是它的预计执行成本更高，因为不能利用索引过滤不符合要求的行。
There is an attribute RUNSTATS TIMESTAMP on the table or index node of the access plan graph that indicates the last time when the statistics were collected.
在访问计划图的表或索引节点上会有一个RUNSTATSTIMESTAMP属性，它表示收集统计数据的时间。
If specified, it requests an access plan using an XISCAN operator over this particular XML index.
如果指定了索引名的话，它将对特定的xml索引使用XISCAN操作符来请求一个访问计划。
Figure 12 confirms that the new index on the STAFF table is being used in the query access plan.
图12确认查询的访问计划中使用了staff表上的新索引。
The index attribute is optional and allows you to specify an index name that will be used as the leading index in an 'IXAND' plan.
index属性是可选的，并允许您指定一个索引名来作为“IXAND”计划中的主索引。
Access plan for query accessing an inverted text index.
访问反向文本索引的查询的访问计划。
To evaluate the new access plan after the index creation on the ACCOUNT table issue.
为了在account表上创建索引之后评估新的访问计划，要发出。
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的索引扫描。
If you are using an IXAND or ACCESS guideline to specify a particular leading index, but are not getting the requested plan, check the following.
如果使用IXAND或ACCESS准则指定了特定的主索引，但是没有获得所请求的计划，那么检查以下内容。
Access plan for query accessing a hash index.
访问hash索引的查询的访问计划。
With the new index created, and statistics collected on it, the optimizer corrects the cardinality estimate of the query access plan.
然后优化器会使用新创建的索引和在其上收集的统计信息来更正查询访问计划的基数估计值。
Access plan for query without inverted text index.
未使用反向文本索引的查询的访问计划。
The leftmost plan (a) is used if there is no eligible index for the predicates in this query.
如果该查询中没有合适的索引用于谓词，则使用最左边的计划(a)。
An XISCAN plan if only a single index is defined on the table and it is of type XML.
一个XISCAN计划，前提是只对表定义了一个单一的索引并且其类型为XML。
Access plan for query without hash index.
不使用hash索引的查询的访问计划。
Access plan for query without hash index.
不使用hash索引的查询的访问计划。
应用推荐