Information about the table space and index node groups or partitions.
关于表空间和索引节点组或分区的信息。
This simple function creates a table node, then iterates through the book list and creates a row for each book, with a cell for each data element.
这个简单函数创建了一个表格节点，然后循环访问书的列表并为每本书创建一行，为每个数据元素分配一个单元格。
For example, an attachment module might record the name, location, and size of a file in its own table, then associate that information with a story node.
例如，一个附件模块可能在它自己的表中记录一个文件的名称、位置和大小，然后将该信息关联到一个故事节点。
There is no FETCH or table node shown in the access path graph because it is an index-only scan.
因为其是一个唯一索引扫描，所以在访问路径图中不显示FETCH或表节点。
You can obtain the statistics from the table descriptor of the table node in the underlying access path graph.
您可以从基础访问路径图中的表节点的表描述符处获得该统计信息。
Additionally, one Node may refer to another Node, in much the same way that an object references another object or a row in one database table references a row in another database table.
此外，一个结点可以引用另一个结点，与在一张数据库表中一个对象引用了另一个对象、一行或是引用了另一张数据库表中的一行类似。
To see the table descriptor, right-click the table node in the access path graph.
为了查看表描述符，请右键单击访问路径图上的表节点。
Table 1 lists the high-level configurations of each physical node.
表1列出每个物理节点的高级配置。
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.
正如在表节点描述符上所显示的，在表空间上有10个分区，且用于九个分区的极限键是625,000个。
The qualifying RIDs are then taken by the fetch node to fetch the corresponding records and data pages from the table space into the DB2 buffer pool.
然后通过FETCH节点获取合格的RID以提取来自表格空间的相应记录和数据页面到db2缓冲池。
There is an attribute RUNSTATS TIMESTAMP on the table or index node of the access plan graph that indicates the last time when the statistics were collected.
在访问计划图的表或索引节点上会有一个RUNSTATSTIMESTAMP属性，它表示收集统计数据的时间。
These RIDs are used by the FETCH node to position the corresponding data pages in the table space.
FETCH节点使用这些 RID来定位表空间内的对应数据页面。
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.
在图2中，表节点的描述符和TBSCAN节点的描述符显示在访问路径图的左侧。
Because the inner table is scanned with TBSCAN, which does not guarantee the expected order for MSJOIN, a SORT node is added to enforce the order.
因为通过TBSCAN扫描内部表，即不能对MSJOIN保证预期的顺序，所以添加sort节点来执行顺序。
The example node name would consist of the components shown in Table 4.
那么，它的节点名应该由表 4 所示的成分组成。
Table 1 also shows a host name called abcdefgh00, which happens to correspond with the node name of the system.
表1中还显示了一个名为abcdefgh00的主机名，它正好与该系统的节点名相对应。
Table 8 shows a desirable node name configuration for a group of eight Oracle servers across two p590-managed systems and the distribution of "hdisk0" traffic across dual VIO servers.
表8给出一个更好的节点名配置方案，其中有8个Oracle服务器分布在两个p 590受管理系统上，“hdisk0”的通信流分布给两个VIO服务器。
Table 1 illustrates a node named abcdefgh00 with five host names.
表1说明了一个名为abcdefgh00的节点具有五个主机名。
Table 5 also shows a host name called "bosapora00," which happens to correspond with the node name of the system.
表5中有一个称为“bosapora00”的主机名，此名称恰好与节点名相同。
Macker said the Manet architecture involves building a routing table in which each node knows not only its neighbors one hop away but also the nodes next to those neighbors.
麦克称，Manet的体系结构包括建立一个路由表，每个节点不仅知道其“单跳”相临节点，还应知道与其他相临节点的下一个节点。
The above command creates a table called tab1, and it will automatically register the node datablade.
以上命令创建名为 tab1 的表格，并且它会自动地注册节点数据刀片。
These eight qualifying RIDs are used by the fetch node to locate the corresponding records and page in the table space, which contains 560273 records.
在表空间上通过提取节点来定位相应的记录和页面以使用这8个合格的RID，其包括560,273条记录。
A Drupal content module typically extends the standard Drupal node with supplemental fields stored in a separate table.
Drupal内容模块通常扩展标准Drupal节点，将补充字段存储在一个单独的表中。
The query in Listing 5 selects all nodes whose text contains "Last Trade," and for each one (I expect only one), outputs a table row containing the contents of the following node.
清单5中的查询语句将选择所有文本内容中包含“LastTrade”的节点，然后为每个节点(希望只有一个)输出一个包含后续节点内容的表格行。
The second leg of the NLJOIN node is similar to that of the first table
NLJOIN节点的第二步类似于第一个表的第二步
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.
对于本例，从数据库浏览器树型视图中选择Employee表节点，然后在该节点上单击鼠标右键，如图5所示。
Define the compute node group in the noderes table, define the compute profile - a profile defines the packages included in a root image - in the nodetype table, as shown in Listing 8.
在noderes表内定义计算节点组，在nodetype表内定义计算概要文件—一个概要文件定义了在一个根映像内所含的包—，如清单8所示。
To delete tables from the Server Explorer tree, right-click on the appropriate table node in the tree, and choose the delete option.
要从Serverexplorer树中删除表，右键单击树中相应的表节点，然后选择Delete选项。
We could then apply a tree manipulation to move the Filter node underneath the Join node toward the related Table node.
随后，我们可以应用一项树操作，将Join节点下方的Filter节点朝着相关Table节点的方向移动。
In a similar vein, with an XML table, you can apply YQL filters to any XML document, combining it with XPath to retrieve specific node collections.
同样地，您可以使用一个xml表向任何xml文档应用YQL过滤器，结合使用XPath检索特定的节点集。
应用推荐