Select all tables for import, then Next.
选择导入所有表，然后单击Next。
This one command performs RUNSTATS on all tables.
这一命令对所有表执行RUNSTATS。
Consider all tables for automatic statistics collection.
考虑对所有表进行自动统计信息收集。
A script might drop all tables and add all of the tables again.
脚本可能会删除所有的表，再添加所有的表。
The export will include all schemas, all tables, all views, etc.
导出的东西包括所有的模式、所有的表和所有的视图等等。
Restore all distinct types followed by all tables with their indexes.
恢复所有不同的类型，然后恢复所有表及其索引。
With the newly created indexes, all tables are accessed with index scans.
有了新建的索引，所有表都可以用索引扫描访问。
Note: Enterprise replication requires that primary keys be defined on all tables.
注意：企业复制要求在所有表上定义主键。
STATCHANGE is the percentage change threshold value for all tables in your system.
STATCHANGE是指系统中所有表的修改阈值，采用百分比形式。
Then click Retrieve and you should get a list of all tables with PPMT schema name.
然后单击Retrieve，就应该获得一个列表，它包含带有PPMT模式名称的所有表。
The analysis on all tables of a database could become cumbersome, if done per table.
如果逐个地对数据库中的所有表进行分析，则分析过程有些烦琐。
This feature removes the need for the DBA to run INSPECT or to reorganize all tables manually.
该特性省去了DBA运行INSPECT或者手动重组所有表的麻烦。
If you omit table name and table schema, information is returned for all tables in the database.
如果您省略了表名和表模式，那么为数据库中的所有表返回信息。
Many large applications use the key manager method to maintain the surrogate keys for all tables.
很多大型的应用程序使用键管理器方法维护所有表的代理键。
The CDR start sec2er command automatically creates replicates for all tables in the user database.
cdrstartsec2er命令自动为用户数据库中的所有表创建复制。
One alternative way of collecting statistics for all tables in a database is to issue a REORGCHK command as follows.
对于数据库中的所有表，收集统计信息的一个可供选择的方法就是发出一条REORGCHK命令，如下所示。
It may still so happen that all tables have unloaded and a few threads are still holding up unloading very large tables.
可能出现大多数表都已经卸载，只有几个线程仍然在卸载非常大的表的情况。
Includes all tables, stored procedures, functions, and views with the ability to exclude objects based on regex patterns.
包括所有表、存储过程、函数和视图，并能基于正则表达式来排除特定对象。
To ensure that the autonumbered id fields get restored to the same value, be sure to drop all tables before you restore them.
为了确保自动编号的id字段被恢复为相同的值，一定要在恢复表前将它们全部删除。
Continue to use the above redistribute continue command with the STOP AT option until you finished redistributing all tables.
继续使用以上的redistributecontinue命令和STOPAT选项，直到重分发完所有的表。
Although collocated tables typically achieve the strongest performance, it is not possible in practice to collocate all tables.
虽然经并置的表通常都会获得最健壮的性能，但是在实际中，不太可能对所有表都进行并置。
A single connection to the DB2 UDB database would be sufficient, since all tables from the IDS database are visible within DB2.
到DB 2UDB的单个连接就已经足够了，因为DB 2中可以看到IDS数据库中的所有表。
If you omit a table name (that is, you specify NULL or an empty string), information is returned for all tables in the schema specified.
如果您省略了表名(即指定NULL或空字符串)，那么为指定的模式中的所有表返回信息。
For all tables and views not fully qualified (no explicit schema is given), the authorization ID of the caller is used as the default schema.
对于所有没有完全限定的表和视图(不带有显式模式)，调用方的授权id被用作默认的模式。
The above example shows that sequential scan and indexes are used to do the data retrieval, and the nested-loop join method is used to join all tables.
以上示例展示了如何使用连续扫描和索引来进行数据检索，以及如何使用嵌套循环连接方法来连接所有表。
Since DB2 z/OS utilities run at either table space level or partition level for partitioned-table space, they would affect all tables present in the table space.
由于DB2z/OS实用程序在分区表空间的表空间级或分区级运行，所以它们会影响表空间中存在的所有表。
Never use the high mode for an entire database or all tables in a database or even all columns in a table unless the database or the tables are of a considerably smaller size.
除非数据库或表的规模很小，否则不要对整个数据库、一个数据库中的所有表或一个表中的所有列使用high模式。
If there is an index on the join column, the costs will be significantly less; otherwise the database server must perform table scans for all tables, both outer and inner tables.
如果连接列上有一个索引，那么其成本会相当低；否则，数据库服务器就必须对所有表(外部和内部表)执行表扫描。
While this problem sounds a bit far-fetched, we've seen it in practice enough times to know that all tables should be in the same database unless there's a pressing reason otherwise.
尽管该问题听起来有些牵强，但是在实践中我们通常总结出所有的表应该在同一个数据库中，除非有非常迫不得已的理由。
The potential drawback of the approach described in this section is that all the data in all the columns in all tables in the entire database are treated in a case-insensitive manner.
本节介绍的方法有一个潜在的缺点：整个数据库中所有表中的所有列中的所有数据都是不区分大小写的。
应用推荐