Step 2.1: Examine the query execution plan.
步骤2.1：检查查询执行计划。
Step 1.1: Examine the query execution time.
步骤1.1：检查查询执行时间。
Enables or disables a query execution trace.
启用或禁用一个查询执行跟踪。
This interface is invoked before every query execution.
在执行每个查询前，会调用此接口。
Such rules can significantly reduce query execution time.
这些规则可以显著减少查询执行时间。
The query execution plan can be viewed using the db2exfmt tool
这个查询执行计划可以使用db2exfmt工具查看
Illustrates how to interpret a federated query execution plan.
阐释如何解释联邦查询执行计划。
Names of existing indexes that are used for query execution by db2.
DB2用于查询执行的现有索引的名称。
The TRACEONLY option disables the display of query execution results.
TRACEONLY选项禁止显示查询执行结果。
Names of existing indexes that are not used for query execution by DB2
DB2未用于查询执行的现有索引的名称
Each connection thread also performs authentication and query execution.
每个连接线程还执行身份验证和查询执行。
A parameterized query binds the value of the parameter before the query execution.
参数化查询在查询执行之前绑定参数的值。
These visualizations include cost based information derived from the query execution.
这些可视化包括来自查询执行的基于成本的信息。
You can analyze the query execution plan output to decide whether or not this is necessary.
您可以分析查询执行计划输出，以确定这是否是必需的。
All SQL comparisons, SQL query execution, and SQL casting takes place in the database code page.
所有SQL比较、SQL查询执行以及SQL类型转换都必须在数据库代码页中进行。
Range producer function to define the search ranges for the spatial index during query execution.
用于定义在查询执行期间空间索引的搜索范围的范围生成器函数。
According to the overall query execution plan, the sub operations are then applied at the sources.
根据总体查询执行计划，将随后对数据源执行各个子操作。
The main focus of this group, however, is to avoid full document decompression during query execution.
这类压缩器主要侧重于避免在查询过程中进行完整的文档解压缩。
This section illustrates how each partitioning feature contributes to the performance of query execution.
本节阐释每个分区特性对查询执行性能的作用。
The main database configuration parameter settings that affect the query execution plan were set as follows
影响查询执行计划的主要数据库配置参数设置如下
Intuitively, an access path is a procedural description of query execution that consists of three components.
直观地说，访问路径是查询执行的程序说明，其包括三个组件。
The DB2 Optimizer is data-partition aware, and only relevant data partitions are scanned during query execution.
DB 2优化器能够感知分区，在执行查询时只扫描相关的数据分区。
This utility will generate a file called sqexplain.out, and records in detail every step of the query execution.
该实用程序将生成一个名为sqexplain . out的文件，并详细记录查询的每个执行步骤。
REOPT once: query optimization occurs once at query execution time, when the query is executed for the first time.
REOPT ONCE：查询执行中只发生一次查询优化，即在查询第一次执行时。
The next two columns represent the query execution time in seconds when MQTs are disabled and when MQTs are enabled.
下两列表示禁用MQT和启用MQT时以秒为单位的查询执行时间。
Now take a look at the three new operators and how they work together with XML indexes in a query execution plan.
现在看一下这三个新操作符，以及它们与xml索引在执行计划中是如何工作的。
At this step, you need to dig into the statistics you collected above and take a good look at the query execution plan.
在这一步中，需要挖掘上面所收集的统计数据，并仔细查看查询执行计划。
The following shows how an optimization guideline can specify the runtime degree for a query and affect the query execution.
下面的代码展示了优化指南如何为查询指定运行时等级以及如何影响查询的执行。
Like standard queries, answer solution queries are subject to query execution enforcement as specified by security policies.
与标准查询一样，回答解决方案查询也受到安全策略指定的查询执行条件的控制。
The DB2 9.5 optimizer USES both type of indexes to optimize the queries and help selecting the best plan for query execution.
DB 2 9.5优化器使用两种类型的索引来优化查询，并帮助选择最佳的查询执行计划。
应用推荐