Find the top join node in a query plan.
查找一个查询计划中的顶级连接节点。
This query plan shows full table scans.
该查询计划显示了全表扫描。
This query plan shows a full table scan.
该查询计划显示了一个全表扫描。
Use SQL directives to effect the query plan.
使用SQL指令实现查询计划。
This query plan shows the use of a functional index.
该查询计划展示了函数索引的使用。
This query plan shows an index scan using our functional index.
该查询计划显示索引扫描使用了函数索引。
Static queries have already been parsed, and had a query plan generated.
静态查询已经经过解析,并生成了查询计划。
Hence, the need for statistical views arises in query plan optimization.
因此,在进行查询计划优化时,就需要使用统计视图。
set explain on directs IDS to generate a file that shows the query plan.
setexplainon 指示IDS生成显示查询计划的文件。
When a static query is executed, the previously computed query plan is used.
当执行静态查询时,会使用以前生成的查询计划。
The optimizer USES the following system catalog information as it creates a query plan.
当优化器创建查询计划时,它将使用下列系统目录信息。
The value ANY allows the optimizer to determine the number of ATQs for a given query plan.
值ANY允许优化器决定一个给定查询计划的 ATQ的数量。
This query plan uses hash join for each join between the fact table and a dimension table.
这个查询对每个事实表和维度表之间的连接使用散列连接。
We can then examine the equivalent symbolic tree representation of this query plan in Figure 1.
随后,我们可以查看图1,其中展示了这个查询计划的等效符号树表示形式。
It's a right-deep query plan such that for each hash join, the build table is a small dimension table.
每个散列连接都是右深查询,构建的表是一个小的维度表。
The query plan information shown in the following examples is taken from the sqexplain.out file for this query.
以下示例中显示的查询计划信息来自这个查询的sqexplain.out文件。
Conceptually, rows of relational data (tuples) flow through the operation nodes in the query plan from bottom to top.
从概念上来说,关系数据行(元组)按照自下向上的方式流过查询计划中的操作节点。
As this query plan shows, keys from more than one hash table build can be pushed down to filter rows of the fact table.
如这个查询计划所示,不止一个散列表的键可以被下推来过滤事实表的行。
Enables or disables query plan tracing, also known as a plan tree, which captures the transformation process of a query.
启用或禁用查询规划跟踪,也称为规划树,它捕获一个查询的转换流程。
After the optimizer has done its work, the compiler converts the query plan into executable code segments called snippets.
优化器完成工作后,编译器将把查询计划转换为可执行的代码段,称为snippet。
This command updates the statistics in the system catalogs that the optimizer USES to determine the lowest-cost query plan.
此命令更新了系统目录中的统计数据,优化程序使用这些数据来确定成本最低的查询计划。
To ensure that the optimizer selects the best query plan, it is important to keep internal statistics current and accurate.
为了确保优化器选择最佳的查询计划,使内部统计数据保持为最新并且最准确的十分重要。
The optimizer chose this query plan because the estimated cost for its execution was the lowest among all the evaluated plans.
优化器将选择该查询计划,因为其执行的估算成本是所有被估计划中最低的。
The optimizer would chalk out a query plan before performing the actual join operation itself by making use of the statistical data.
在执行实际的连接操作之前,优化器使用统计数据制定一个查询计划。
A query plan ideally is an optimal plan to execute the given query - that is, it determines the most efficient way to fetch the data.
理想情况下,查询计划是执行给定查询的最佳计划—也就是说,它会确定抓取数据的最佳方式。
To ensure that the optimizer selects a query plan that best reflects the current state of your tables, run UPDATE STATISTICS at regular intervals.
为确保优化器选择的查询计划能够最好地反映表的当前状态,应定期运行UPDATESTATISTICS。
You can delve deeper into how a query is written by prepending EXPLAIN to the query, which will return the query plan instead of the result set, as show in Listing 2.
您可以更深入地钻研如何写查询,即在查询开始处加上EXPLAIN,它会返回查询计划,而非结果集,如清单 2 所示。
For our purposes, it suffices to understand that asynchrony is introduced into a federated query plan by the optimizer's judicious placement of the TQ (Table Queue) operator.
就我们此处的目的而言,只要理解异步是通过优化器明智地放置TQ(表队列)操作符而引入到联邦查询计划之中的就足够了。
It helps eliminate the costs of traditional performance tuning, such as indices, materialized query tables (MQTs), and query plan tuning that required extensive time and expensive resources.
它有助于消除传统性能调优的成本,比如索引、物化查询表(Materialized Query Table,MQT)、以及需要大量时间和昂贵资源的查询计划调优。
Consequently, if the statistics are inaccurate, outdated, or conflicting, the optimizer will create inaccurate estimates for the costs of the steps in a query plan, leading to poor performance.
因此,如果统计数据不准确或者过期,或者冲突,优化器会对查询计划中各步骤的成本评估不准确,从而导致糟糕的性能。
应用推荐