为了查看表描述符，请右键单击访问路径图上的表节点。
To see the table descriptor, right-click the table node in the access path graph.
展开主资料表节点，并选取相关资料表的详细资料节点。
Expand the master table node and select the detail node for the related table.
您可以从基础访问路径图中的表节点的表描述符处获得该统计信息。
You can obtain the statistics from the table descriptor of the table node in the underlying access path graph.
因为其是一个唯一索引扫描，所以在访问路径图中不显示FETCH或表节点。
There is no FETCH or table node shown in the access path graph because it is an index-only scan.
在访问路径图中的三个表节点上显示的数字从记录的数量方面说明了表的大小。
The Numbers that appear in the three table nodes in the graph indicate the size of the table in terms of number of records.
在图2中，表节点的描述符和TBSCAN节点的描述符显示在访问路径图的左侧。
In Figure 2, the descriptor for the table node and the descriptor for the TBSCAN node are shown to the left of the access path graph.
nodeType是代表节点类型的整数——例如，2代表属性节点，7代表处理指令。
NodeType is an integer representing the node type — for example, 2 for an attribute node and 7 for a processing instruction.
要从Serverexplorer树中删除表，右键单击树中相应的表节点，然后选择Delete选项。
To delete tables from the Server Explorer tree, right-click on the appropriate table node in the tree, and choose the delete option.
正如在表节点描述符上所显示的，在表空间上有10个分区，且用于九个分区的极限键是625,000个。
As shown in the table node descriptor, there are 10 partitions in the table space, and the limit key for the ninth partition is 625,000.
对于本例，从数据库浏览器树型视图中选择Employee表节点，然后在该节点上单击鼠标右键，如图5所示。
For this example, select the Employee table node from the database explorer tree view, and click the the right mouse button on that node, as shown in Figure 5.
关于表空间和索引节点组或分区的信息。
Information about the table space and index node groups or partitions.
展开此连接节点以根据指定的文件夹过滤器显示数据库对象的各个节点(表、视图、函数、过程)。
Expand the connection node to display the various nodes for the database objects (tables, views, functions, procedures) depending on the folder filters that were specified.
为提高性能，从磁盘读取的样式表缓存在内存中——节点不能缓存输入消息提供的样式表。
To improve performance, stylesheets read from disk are cached in memory - the node does not cache stylesheets that are supplied in the input message.
加载了样式表并执行转换之后，节点要将结果重新解析为消息树。
After the style sheet is loaded and transformation is performed, the node re-parses the result into a message tree.
那么，它的节点名应该由表4 所示的成分组成。
The example node name would consist of the components shown in Table 4.
表1列出每个物理节点的高级配置。
Table 1 lists the high-level configurations of each physical node.
PDGP分区组跨越数据节点，这是表空间所在的位置。
The PDGP partition group spans the data nodes, which is where the table Spaces are placed.
当使用样式表转换节点时，样式表对WSDL中各个元素间的XML注释布局很敏感。
When using the stylesheet transform node, the stylesheet is sensitive to the layout of XML comments between elements in the WSDL.
样式表中的元素直接映射成树上的节点，如表1 所示。
Elements in the style sheet map directly to nodes on the tree, as shown in Table 1.
自动在新节点上创建表。
表1：节点名和主机名。
执行下列SQL，以找到跨节点的表的分布。
Execute the following SQL to find out the distribution of your table across the nodes.
此功能使用IBMexplorer树中的表和视图节点上的RetrieveData菜单选项公开。
This functionality was exposed using the Retrieve Data menu option on the table and view nodes in the IBM Explorer tree.
在nodehm表内定义节点的硬件管理，如清单9所示。
Configure the hardware management of the nodes in the nodehm table, as shown in Listing 9.
对齐：左对齐(确保表的页节点仍然被选中)。
如果那些表不存在，那么可以通过另一个选项使用主复制在目标节点上创建这些表。
You also have the option to create tables on target nodes using master replicates if those tables are not already present.
模板可以使用主节点上的主复制字典在其他节点上创建表，以确保大量节点之间模式的一致性。
Templates can use the master replicate dictionary from the master node to create tables on other nodes to ensure consistent schemas among large Numbers of nodes.
虽然从上下文节点出发沿着某个轴仍然只能按照文档顺序返回节点，但是得到节点之后样式表可以根据需要重新排列节点。
Following an axis from a context node will still return nodes in document order, but once it has those nodes, your stylesheet can reorder them as it requires.
此图表包含表示表、索引、操作和返回数据的节点。
The diagram consists of nodes that represent tables, indexes, operations, and returned data.
表1和2代表在每个节点上所需备份的数据。
Tables 1 and 2 represent data you need to back up on each node.
应用推荐