The query optimizer does not recalculate the profile for tables automatically.
查询优化器不会自动重新计算表的配置文件。
The query optimizer will try to reduce the number of messages sent to the data source.
查询优化器将尝试减少发送到数据源的消息的数量。
STEP d: We need to explain the queries to view the access plans chosen by the DB2 query optimizer.
第4步:我们需要对查询进行explain(解释),以查看DB 2查询优化器所选择的访问计划。
These views include columns containing statistical information that is useful to the query optimizer.
这些视图包括一些包含对查询优化器有用的统计信息的列。
The query optimizer bases query-cost estimates on the number of rows to be retrieved from each table.
查询优化器根据从每个表检索的行数估计查询成本。
Given accurate statistics, the query optimizer generally comes up with correct selectivity estimates.
如果有了准确的统计信息,那么查询优化器一般能够得出正确的选择性估计。
The output of the query optimizer on a federated system is the Federated Query Execution Plan (FQEP).
联邦系统上查询优化器的输出是联邦查询执行计划(FederatedQuery Execution Plan,FQEP)。
During plan generation for the query, the query optimizer communicates with the non-relational wrapper.
在为查询生成计划的过程中,查询优化器与非关系包装器通信。
A new feature of the query optimizer supports a new type of index scan, called an index self-join path.
查询优化器的一项新特性支持一种新的索引扫描,即索引自连接路径。
The query optimizer relies heavily on these statistics — especially card, colcard, high2key and low2key.
查询优化器很大程度上依赖于这些统计信息——尤其是card、colcard、high2key和low2key。
Accurate index information and statistics are fundamental to cost-based decisions in the query optimizer.
准确的索引信息和统计信息是查询优化器中基于成本的决策的基础。
With this feature, the query optimizer can immediately consider the index when determining an access plan.
有了这个特性,查询优化器可以在决定访问计划时立即考虑索引。
An entry is added to the system catalog to indicate to the query optimizer that such a remote index exists.
一个条目被添加到系统编目中,以向查询优化器表明存在那样的一个远程索引。
Visual Explain also includes information on the database objects considered and chosen by the query optimizer.
VisualExplain还包括关于查询优化器所考虑和选择的数据库对象的信息。
The query optimizer also tries to reduce the number of messages sent to the data source if the network is slow.
如果网络较慢,查询优化器还尝试减少发送到数据源的消息数量。
The push-down decision is made by the wrapper during the planning phase, while working with the query optimizer.
下推的决定是包装器在计划阶段与查询优化器一起做出的。
Can perform faster with the creation of a keyed logical file containing the keys suggested by the query optimizer?
按照查询优化器建议的键创建逻辑文件能够执行得更快。
In general, the query optimizer selects a plan that will return the entire result set in the shortest amount of time.
通常,查询优化器选择将在最短时间内返回整个结果集的计划。
The SQL explain facility provides detailed information about the access plan that the query optimizer chooses for an SQL statement.
SQL解释工具提供查询优化器为 SQL语句所选择的访问计划的有关详细信息。
Regardless of schema (3nf or Star), the Teradata query optimizer relies on statistics to help it determine the best way to access data.
不管哪种模式(3nf或Star),Teradata查询优化器依赖于统计信息帮助确定最佳数据访问路径。
This allows the query optimizer to do a better job of analyzing the complex query, as the statistics can now closely reflect the actual cost.
这使得查询优化器可以更有效地分析复杂的查询,因为现在统计信息近似地反映实际成本。
Rebind applications that use static SQL after using RUNSTATS so that the query optimizer can choose the best access plan given the new statistics.
在使用RUNSTATS之后需要重新绑定使用静态SQL的应用程序,这样查询优化器就可以选择新统计信息所给出的最佳存取方案。
Selectivity: When the query optimizer (QO) studies your SQL, the degree of selectivity determines if an index should be used to perform the operation.
选择性:当查询优化器(query optimizer,即QO)读取SQL时,选择性的程度决定了索引是否应该用来执行该操作。
When this option is set, the query optimizer chooses the query execution plan that pushes the most work down to the data source as indicated by the PDA component.
当设置了该选项时,查询优化器选择按照PDA的指示将大部分工作下推到数据源的查询执行计划。
When the following query is issued, the query optimizer will detect that the query can be answered using an MQT, and may choose an access plan that accesses the MQT.
当发出下面的查询时,查询优化器将检测到该查询可以用一个MQT来回答,因而可能会选择访问该MQT的一个访问计划。
You should also consider executing runstats on the MQT, so that the query optimizer has accurate information about the number of rows in the MQT and other statistics.
您还应该考虑在MQT 上执行runstats,以便查询优化器拥有关于 MQT 中的行数以及其他统计信息的准确信息。
Programmers can work transparently with data from these various sources, relying on DB2 II's global query optimizer to select an efficient data access strategy for such work.
程序员可以透明地使用来自这些不同数据源的数据,并通过DB2II全局查询优化器来选择一个有效的数据访问策略。
The query optimizer USES the SYSSTAT catalog views in the database to retrieve the statistical information of the database objects and determine the best way to access the data.
查询优化器使用数据库中的SYSSTAT目录视图来检索数据库对象的统计信息,并确定访问数据库的最佳方法。
The query optimizer might come up with a different query execution plan tailored to provide good performance for fast retrieval of first 'n' rows rather than all the result rows.
查询优化器可能得出一个不同的查询执行计划,这个计划可以专门为最快地获取前'N '行,而不是所有结果行提供良好的性能。
Note: the query optimizer considers using a functional index when the index expression is used in a relational expression or as an argument to one of the operator class functions.
注意:当索引表达式被用于关系表达式,或作为某个操作符类函数的参数时,查询优化器将考虑使用函数索引。
应用推荐