Figure 7 shows the execution plan.
图7展示了执行计划。
The original query and its execution plan.
原始查询及其执行计划。
The optimized query and its execution plan.
优化的查询及其执行计划。
Step 2.1: Examine the query execution plan.
步骤2.1：检查查询执行计划。
Design the data quality analysis execution plan.
设计数据质量分析执行计划。
Making the decision and developing an execution plan.
做出决定并开发一个执行计划。
The query execution plan can be viewed using the db2exfmt tool
这个查询执行计划可以使用db2exfmt工具查看
Illustrates how to interpret a federated query execution plan.
阐释如何解释联邦查询执行计划。
The execution plan output after the optimization showed a significant improvement.
优化后的执行计划输出显示出了极大的提高。
Subsequent invocations will not peek and the previous execution plan will be reused.
后续调用不会再探测，而是重用之前的执行计划。
If you have indexes for both predicates you may see execution plan (c) in Figure 2.
如果有用于两个谓词的索引，则可以参看图2中的计划(c)。
You can use the output of Visual Explain or db2exfmt to obtain the query execution plan.
您可以使用VisualExplain或db 2 exfmt的输出来获得查询执行计划。
Record details of your test, such as changes you made, response time, and execution plan.
记录测试细节，例如您所做的修改、响应时间和执行计划。
You can analyze the query execution plan output to decide whether or not this is necessary.
您可以分析查询执行计划输出，以确定这是否是必需的。
With asynchrony disabled, a likely execution plan for the query from the motivation section is.
当禁用异步时，异步的动机小节中的查询的执行计划很可能是这样的。
Subsequent invocations will simply keep executing the same execution plan. Let's use an example.
因此，在第一次编译sql语句之后，后来的调用只要继续执行相同的执行计划即可。
The 'legs' of the UNION are processed one at a time, in left-to-right order in the execution plan.
在执行计划中，UNION的几条'分支'是按照从左到右的顺序一个一个地处理的。
According to the overall query execution plan, the sub operations are then applied at the sources.
根据总体查询执行计划，将随后对数据源执行各个子操作。
What if you know your OLTP searches should use the same execution plan for different binding values?
要是你知道你的OLTP搜索对不同绑定值应该使用相同执行计划又该怎么办呢？
From the data quality criteria identified, the data analyst must now design the data execution plan.
识别出数据质量标准之后，数据分析师就必须设计执行计划。
The output of the query optimizer on a federated system is the Federated Query Execution Plan (FQEP).
联邦系统上查询优化器的输出是联邦查询执行计划（FederatedQuery Execution Plan，FQEP）。
The main database configuration parameter settings that affect the query execution plan were set as follows
影响查询执行计划的主要数据库配置参数设置如下
As part of the data quality analysis, an execution plan has been formulated as noted in part 6 of this series.
作为数据质量分析的一部分，执行计划已经被公式化，如本系列第6部分所述。
Now take a look at the three new operators and how they work together with XML indexes in a query execution plan.
现在看一下这三个新操作符，以及它们与xml索引在执行计划中是如何工作的。
Section explains and section actuals are very powerful features to investigate problems with a query execution plan.
在研究查询执行计划的问题时，片段解释和片段实绩是非常强大的特性。
As part of the execution plan, investigation tests will be identified that meet the project-level data requirements.
在执行计划中，需要确定满足项目级数据需求所需的测试。
At this step, you need to dig into the statistics you collected above and take a good look at the query execution plan.
在这一步中，需要挖掘上面所收集的统计数据，并仔细查看查询执行计划。
XSCAN is not an "XML table scan" but it can appear in an execution plan after a table scan to process each of the documents.
XSCAN不是 “XML表扫描”，但在表扫描之后，它可以出现在执行计划中，用来处理每个文档。
The query optimizer will give priority to an execution plan involving an MQT over a plan that involves access to remote tables.
对于涉及到MQT 的执行计划，并且该 MQT 是涉及远程表访问的计划上的 MQT，查询优化器给予它优先权。
Note that the execution plan indicates that the left leg of each hash join will return about 800,000 rows, a significant number.
注意，执行计划表明，每个散列连接的左边分支将返回大约800,000行，这是一个相当大的数字。
应用推荐