When translating this relationship back to the JDBC DMS metadata, you must define both tables before establishing the relationship.
如果要将这种关系重新转换为JDBCDMS数据，您必须在建立关系之前定义两个表。
Once you have settled on DMS table Spaces, you can furthermore choose between raw devices or file system based containers for the table space.
一旦将数据放在dms表空间上，就可以根据表空间的容器进一步选择是使用原始设备还是文件系统。
Data objects are generic and provide a common view of structured data built by a DMS.
数据对象是通用的，它们提供了DMS创建的结构化数据的公共视图。
The DMS is a component that provides methods to populate a data Graph. It saves the changes back to the data source.
DMS是一种组件，它负责提供某些方法来组装数据图，也负责将数据更改保存回数据源。
There was no apparent effect from varying extent size with DMS.
使用DMS 时，更改区段大小并没有明显的效果。
Once some data is modified and the client wants to save its changes, it sends the altered Data Graph to the DMS. Then the DMS updates the data source.
如果数据被修改，而且客户机希望能保存这些更改，它会将更改后的数据图发送给DMS，然后由 DMS 去修改数据源。
For DMS device container tablespaces, the operating system does not cache pages in the file system cache.
对于DMS设备容器表空间，操作系统不在文件系统缓存器中缓存页面。
The containers used in DMS must be a pre-allocated file or physical device, such as a hard disk drive.
DMS中所使用的容器则必须是预分配的文件或物理设备，如硬盘驱动器。
Automated storage is not really a separate type of table space but a different way of handling DMS storage.
自动存储实际上并不是一种表空间，而是另一种处理DMS存储的方法。
DMS usually has better performance and provides the flexibility of storing indexes and LOB data separately.
DMS通常有更好的性能，并且它提供了分别地存储索引和LOB数据的灵活性。
As a rule of thumb for OLTP applications, use DMS tablespaces with multiple devices.
作为OLTP应用程序的经验法则，可在多个设备上使用dms表空间。
DMS table Spaces are managed by DB2, and can be files or raw devices.
dms表空间由DB 2管理，既可以是文件，也可以是原始设备。
With DMS tablespaces, DB2 has more control over how data pages are physically mapped in disk space groupings known as extents.
通过dms表空间，DB2更加可以控制如何将数据页面物理映射到称作区段的磁盘空间分组中。
Behind the scenes, SDO-capable tools and DMS will deal with all the specific and cumbersome data source semantics.
取而代之的是在幕后由支持SDO的工具和DMS来处理所有特定而繁琐的数据源语义。
As a key prerequisite, be sure to use DMS table Spaces with a large page size (see Tip 2).
务必使用具有较大页宽的dms表空间(见提示2)，这是一个关键的先决条件。
So, for this example we've designed our own DMS interface that provides two methods, as shown in Listing 1.
因此我们为这个例子设计了自己的DMS接口，它包含两个方法，如清单1所示。
Containers can be added to, or dropped from, a DMS table space, and their sizes can be modified.
可以将容器添加到dms表空间，或者从dms表空间中删除容器，而且可以更改容器的大小。
This option can only be used for database managed tablespace (DMS).
这个选项仅可用于数据库托管表空间（DMS）。
The physical metadata typically does not affect SDO clients; however, it does affect DMS, which are responsible for data source accesses.
典型情况下，物理元数据并不会影响SDO客户机，但是它会影响到DMS, DMS是负责访问数据源的组件。
DMS containers require more maintenance, and automatic storage was introduced in DB2 V8.2.2 as a way of simplifying space management.
dms容器需要更多的维护，而自动存储是在DB 2V8.2.2引入的，它是一种简化空间管理的方法。
Unless explicitly specified, new table Spaces are created as DMS with large row IDs.
除非显式指定，否则新创建的表空间都是具有较大行id的DMS。
In this benchmark, a moderate page size, 16kb, was chosen for all DMS tablespaces.
在该基准测试中，为所有dms表空间选择了一个16kb的中等页面大小。
Figure 3 shows the employee hierarchy the DMS is using.
图3显示了DMS正在使用的雇员层次结构。
These automatic storage table Spaces actually use the DMS FILE infrastructure and have auto-resize turned on by default.
这些自动存储表空间实际上使用DMSFILE基础设施，并默认自动调整大小。
In DB2 9, newly created table Spaces are DMS by default.
在DB 29中，默认情况下，新创建的表空间是DMS。
Database managed space (DMS) : DMS table Spaces are managed by DB2.
数据库管理的空间(DMS)： dms表空间是由DB 2管理的。
The SDO client instantiates a DMS and gets data graphs for various employees from it.
SDO客户机例示了DMS，并从中获得不同雇员的数据图。
The data format (model) of the data graph can be considered a contract between the DMS and the client.
可以将数据图的数据格式(模型)看作DMS与客户机之间的抽象。
Basically, when an SDO client needs to retrieve data, it USES the DMS to require a data graph. The DMS manages the data source access and creates a graph with the information received.
基本上，当一个SDO客户机需要检索数据时，它使用DMS来请求数据图，DMS负责管理对数据源的访问，并根据接收到的信息来创建一个图，通常这个图是一个分层的树结构，其中包含了几个数据对象。
So a major portion of the performance improvement can be attributed to the pre-allocation of the pages in DMS.
所以，性能提升的很大一部分要归功于DMS 上页的预先分配。
应用推荐