RUNSTATS in partitioned databases.
分区数据库中的runstats。
RUNSTATS with a statistics profile.
包含统计信息配置文件的runstats。
如果没有，则启动runstats。
RUNSTATS with column group statistics.
包含列组统计信息的runstats。
RUNSTATS authorization and user access.
包含授权和用户访问的runstats。
RUNSTATS with system page-level sampling.
带有系统页级抽样的runstats。
RUNSTATS on declared global temporary tables.
已声明的全局临时表上的runstats。
Runstats and common DB2 tuning have been done.
完成runstats和一般的DB 2优化。
RUNSTATS with frequency and quantile statistics.
包含频率和分位数统计信息的runstats。
This one command performs RUNSTATS on all tables.
这一命令对所有表执行RUNSTATS。
Each line is a runstats command on a table or index.
每一个行是一个表或索引上的runstats命令。
Avoid running RUNSTATS on tables that don't need it.
避免在不需要它的表上运行RUNSTATS。
Step 7: Collect statistics over MQTs using runstats.
步骤7：使用runstats收集MQT上的统计信息。
Which means RUNSTATS was never executed on this table.
这意味着该表从未执行过RUNSTATS。
This article mainly USES DB2 and runstats as our example.
本文主要使用DB2和runstats作为我们的示例。
If priority is set to zero, RUNSTATS will run unthrottled.
如果将优先权设置为零，也能不加调整地运行RUNSTATS。
Strategies to reduce RUNSTATS impact on system performance.
减小runstats对系统性能影响的策略。
Currently, the RUNSTATS command is not supported for nicknames.
目前，RUNSTATS命令对于昵称而言还不受支持。
Thus, continue to use RUNSTATS as you would for relational data.
因此，像对待关系数据那样，继续使用RUNSTATS。
In most cases, a RUNSTATS is done after an index has been created.
大多数情况下，RUNSTATS是在创建索引之后执行的。
REORGCHK can also invoke RUNSTATS before examining the statistics.
REORGCHK还可以在检查统计信息之前调用RUNSTATS。
For small tables, issuing the RUNSTATS command would be a trivial task.
对于较小的表，发出RUNSTATS命令将是一项普通任务。
The following examples illustrate using RUNSTATS to collect statistics.
下列例子说明如何使用RUNSTATS收集统计信息？
Q: Can statistics be collected for an individual partition using RUNSTATS?
Q：能否利用RUNSTATS得到单个分区的统计信息？
If the catalog statistics are inaccurate, get them up to date with RUNSTATS.
如果编目统计数据不准确，应该使用RUNSTATS更新它们。
RUNSTATS collects the necessary data to calculate the savings through NULL values.
RUNSTATS收集必要的数据，以计算通过null值节省的空间。
It is allocated when the RUNSTATS utility is started, then freed when it completes.
它是在启动RUNSTATS实用程序时分配的，然后当它完成时释放。
Avoid running RUNSTATS on an empty database, as this will lead to poor performance.
避免在空数据库上运行RUNSTATS，因为那将导致低劣的性能。
Implement multiple concurrent RUNSTATS on different partitions for different tables.
对于不同的表，在不同的分区上实现多个并发的RUNSTATS。
You can specify the number of frequent values and quantiles on the RUNSTATS command.
只需要指定RUNSTATS命令的频率值和分位数。
应用推荐