该方法结合内存表和磁盘表两种机制，不但提供快速的性能，而且解决了内存表的永久保存问题。
This method combines memory-based table with disk-based table, it not only provides good performance, but also solves the problem of memory table's permanent storage.
因此，它需要消耗大量的磁盘空间，当表比较大时这一点尤为明显。
Therefore, it consumes a lot of disk space, especially when the table is too big.
它提供持续的表重组，并且不需要传统的影子复制方法所需的额外磁盘空间。
It provides a continuous reorganization of a table without the excess disk space associated with the traditional "shadow" copy approach.
降低磁盘资源争用的另一种可行办法是将信息传递引擎数据表和日志移动到文件系统中其他更快的驱动器上，或者使用远程消息传递数据库。
Another possible way to reduce disk contention is to move the messaging engine data tables and logs to separate, faster drives on the file system or use a remote messaging database.
注意：在清单14中，sales_fact表是通过单独一个事务填充完成的，这需要占用大量的磁盘空间来记录日志。
Note: in Listing 14, the SALES_FACT table is populated in a single transaction, which will require a large amount of disk space for logging.
操作系统(包括调页空间)、DB 2日志和DB 2表空间应当拥有各自的专用磁盘。
The operating system (including paging space), DB2 logs, and DB2 table Spaces should each have their own dedicated disks.
有一些技术用来避免UI线程中的长时间运行动作，举一个常见的例子：使用某种数据库查询、网络调用或磁盘进行填充的表或树。
Here are some techniques for avoiding long-running actions in the UI thread, using a common example: a table or tree that is filled from some sort of database query, network call, or disk.
为提高性能，从磁盘读取的样式表缓存在内存中——节点不能缓存输入消息提供的样式表。
To improve performance, stylesheets read from disk are cached in memory - the node does not cache stylesheets that are supplied in the input message.
用于该基准的数据库必须有10tb的原始数据，并且有高效的磁盘扫描和表连接算法。
The database used for this benchmark is defined with 10tb of raw data and requires highly efficient disk scanning and table joining algorithms.
还要通过仔细地将表空间映射到磁盘上来组织好磁盘子系统，从而获得最佳性能。
The disk subsystem is organized for optimal performance by carefully mapping the tablespaces onto the disks.
三个磁盘用于消息传递数据库表空间。
因为db2缓冲池是系统主内存的一部分，DB 2数据库管理器在它读取或写入磁盘介质时将它分配给缓存表和索引数据。
Since a DB2 buffer pool is a part of the main memory of the system, the DB2 database manager allocates it for caching tables and index data when it reads or writes to and from media disks.
为确保优秀的磁盘性能，还需要慎重定义表空间。
The tablespaces were defined carefully to ensure excellent disk performance.
可以通过表空间快照来决定是否将数据真正写入磁盘。
You can use table space snapshots to determine if the data is ever actually written to disk.
MBR是磁盘上的第一个扇区，因而分区表在其中所占空间不大。
The MBR is the first sector on the disk, so the partition table is not a very large part of it.
应当有多个磁盘用于DB 2日志、表和索引。
There should be multiple disks for the DB2 logs, for tables, and for indexes.
此外，如果您有不常用的含多个列的一个表，您也在通过null值字段浪费磁盘空间。
In addition, if you have a table with many columns that aren't typically used, you are also wasting disk space with NULL value fields.
磁盘位置是保存注册表以及队列消息的地方。
The disk location is where the registry will be saved to and any messages for queues.
如果可能，最好对DB2事务日志和DB 2表空间使用不同的磁盘控制器。
If possible, it's even better if you are able to use different disk controllers for DB2 transaction logs and DB2 table Spaces.
分区表位于磁盘主引导记录（MBR）之中。
The partition table is located in the master boot record (MBR) of a disk.
通过在rmobjects表中运行obj_actiondate检查移植到外部磁盘的情况。
Checking on obj_actiondate from the RMOBJECTS table shows objects are migrated to external disks.
外部表中的管道可用于在两个实例之间转移数据并在磁盘空间上保存数据。
Pipes in external tables can be used to transfer data between two instances and save on the disk space.
如前所述，当您在UNIX中创建一个文件系统时，将为inode表分配大约百分之一的总磁盘空间。
As mentioned earlier, when you create a file system in UNIX, about 1 percent of the total disk space is allocated to the inode table.
通常，文件系统磁盘空间中大约百分之一空间分配给了inode表。
Usually, about 1 percent of the total file system disk space is allocated to the inode table.
“notloadedyet”消息表示实际上插件注册表写到了磁盘上，它所引用的部分只是在需要的时候才加载。
The "not loaded yet" message refers to the fact that the plug-in registry is written to disk, and referenced portions of it are reloaded only as needed.
将表空间分布在多个容器(这些容器映射到不同磁盘)。
Spreading tablespaces over multiple containers (which map to separate disks).
如果更多磁盘可用，则实例表应该在三个或更多磁盘上分布。
If more disks are available, the instance tables should be distributed on three or more disks.
磁盘错误、管理员的失误和其他问题可能会破坏关键的磁盘结构(比如分区表)，从而影响一个磁盘上的所有卷。
Disk errors, administrator mistakes, and other problems can affect all the volumes on a disk by wiping out critical disk structures, such as the partition table.
因为TPC - H工作负载中表扫描和表排序的数量较多，所以为获得最佳性能将数据从磁盘预取到内存是很重要的。
Because of the number of table scans and table sorts in the TPC-H workload, prefetching data from disks into memory is important for optimal performance.
所有数据库表和索引都放在内存中，而且永远不会保存到磁盘上。
All database tables and indexes are kept in memory and never saved to disk.
应用推荐