应该在运行表创建脚本之前使用这个命令。
This command should be used before running the table creation script for the subsystem.
目前，要运行表上的RUNSTATS，就要执行全表扫描。
Currently, a full table scan is performed whenever RUNSTATS on table is run.
在运行测试之前，从表中删除数据。
在此文件内，应用程序连接到数据库并针对此目录表运行查询。
It's where the application connects to the database and runs the query against the directory table.
在命令行中对下列三个表运行RUNSTATS，如下所示
Run RUNSTATS on the following three tables from a command line, as follows
避免在不需要它的表上运行RUNSTATS。
可用这一选项来只删除分析数据库中与运行相关的表。
You can use this option to remove only the tables associated with the run in the analysis database.
这说明您没有运行创建数据库表的SQL文件。
What this indicates is that you forgot to run the SQL file that creates the database tables.
运行close_temp删除临时表。
表3.运行包装器脚本获得的各种X平方分布统计信息。
Table 3. Various Chi Square statistics from running the wrapper script.
这与在运行ALTERFRAGMENT 后的表上执行完整的统计刷新是不同的。
This is not equivalent to running a complete statistics refresh on resulting tables of an ALTER FRAGMENT.
假设有一个针对非常大的表运行的查询，它使用同一个缓冲池并且需要读取比总的缓存区大小还多的页。
You might also have a query that runs against a very large table that USES the same buffer pool and involves reading more pages than the total buffer size.
当在会话中设置STATCHANGE后，它将影响该会话中在其上运行updatestatistics的表。
When STATCHANGE is set in a session, it affects the tables on which update statistics is run in that session.
该特性省去了DBA运行INSPECT或者手动重组所有表的麻烦。
This feature removes the need for the DBA to run INSPECT or to reorganize all tables manually.
客户数据库只有一个表，可以通过运行清单6中的脚本创建。
The customer database has a single table that can be created by running the script shown in Listing 6.
表2：在运行时的托管支持系统。
运行导入命令，用几个订单填充此表。
Run the import command to populate your table with a couple of orders.
它选择一个散列连接，以PART作为内部表，这个计划只需运行299秒。
It selects a hash join with PART as the inner table which runs in 299 seconds.
当旧有运行的输出表细节信息不需保留，而需要保留规则的历史记录时，应当使用这一选项来节省分析数据库的空间。
You should use this option to save space on the analysis database when the details of the output table of older runs are no longer needed, while keeping the run history of the rule.
在应用程序会话定义已创建的临时表之后，并发运行的会话不需要重新定义它。
After an application session defines a created temporary table, concurrently running sessions do not have to redefine it.
步骤2：运行脚本来创建所需的表。
来自user表的记录在运行时被转换为一个文本文件。
Record from the USER table is transformed to a text file at run time.
在每次测试运行之后便删除数据库person表中的所有记录。
All the records in the database PERSON table were deleted after each test run.
因此，您需要先创建一张表，然后再运行这段代码。
Therefore, you need to create a table before running this code. Here is the create statement
在 ADMIN_MOVE_TABLE过程运行时，TPCD.PART表是完全可访问的并且分区键的更改对于终端用户是透明的。
While the ADMIN_MOVE_TABLE procedure is running, the TPCD.PART table is fully accessible and the change to the partitioning key is transparent to the end users.
由于没有自动运行UPDATESTATISTICS，所以systemcatalog表没有更新，仍然保留旧的统计数据。
Since the update STATISTICS are not run automatically, the System Catalog tables would not be updated and would still be retaining the old statistical data.
图6显示了运行数据库创建脚本后的事件存储表。
Figure 6 shows the event store table after running the database creation scripts.
为确保优化器选择的查询计划能够最好地反映表的当前状态，应定期运行UPDATESTATISTICS。
To ensure that the optimizer selects a query plan that best reflects the current state of your tables, run UPDATE STATISTICS at regular intervals.
如果要使对过滤表的更改生效，需要在运行此命令时带上一些参数。
For the changes done to the filters table to take effect, you'll have to run this command with some arguments.
如果要使对过滤表的更改生效，需要在运行此命令时带上一些参数。
For the changes done to the filters table to take effect, you'll have to run this command with some arguments.
应用推荐