传统的内存数据库要求内存数据库能容纳全部外存数据库，因此没有数据装入的问题。
The traditional MMDB assumes that the entire database is stored in volatile main memory, so there is no trouble of data loading.
代码是使用称为HSQLDB的内存数据库测试的，这种产品包含一个简单的GUI工具。
The code was tested using an in-memory database called HSQLDB, and this product includes a simple GUI tool.
而要实现内存受限的内存数据库，就是在内存数据库不能容纳全部外存数据库的前提下，保证一个事务执行前，其数据被装入内存。
But the MMDB with limited main memory should assure that before running a transaction, all data accessed by it should be loaded into the main memory.
当您设计缓冲池时，您应该考虑数据库的内存需求。
When you design buffer pools, you should consider the database memory requirements.
这比其他UNIX平台上可用的任何数据库共享内存集要少得多。
This is much less then any database Shared memory set available to other UNIX platforms.
数据库共享内存的限制大约是 3.5GB。
这不仅仅是临时的内存中的数据库；而是永久保存在磁盘中。
This is not just some transient in-memory database; it is persisted to disk.
但是，这意味着数据库a的数据库内存必须调出。
But this means the database memory for database a must be paged out.
在激活数据库的时候分配该内存。
注意这个数量同时还包括实例共享内存和数据库共享内存，并且它们的内存段必须是邻接的。
Note this amount includes both the instance Shared memory and database Shared memory, and their memory segments must be contiguous.
输出显示了SAMPLE数据库使用的内存。
运行数据库所需的内存。
每多一个服务器，就意味着将有更多的CPU、内存和更多的磁盘用于分区数据库。
Each additional server means more CPUs, more memory, and more disks for your partitioned database.
在DB 2LUW中，DB 2服务器所消耗的内存大致分为实例级的数据库管理器共享内存和数据库级的数据库共享内存。
In DB2 LUW, memory consumed by DB2 server is broadly sub-divided into instance-level database manager Shared memory and database-level database Shared memory.
最常见的内存中数据库索引策略是T -树。
The most common in-memory database index strategy is called T-tree.
数据库缓冲池通常是数据库共享内存中最大的一块内存。
The database buffer pool(s) area is normally the largest component of the database shared memory.
可以在一个简单的Python脚本中实现整个程序，使用内存中的 “数据库”。
You can do the whole thing in one simple Python script with an in-memory "database."
有两种可能会立即出现在您的脑海中：开源的内存中的SQL数据库hsqldb和XQuery。
Two possibilities immediately sprang to mind; HSQLDB, the open-source in-memory SQL database, and XQuery.
对于用于数据库的数据库内存，名称为db。
换句话说，不能激活数据库或连接到数据库，因为没有足够的共享内存来满足请求。
In other words, the database failed to activate or connect because there was not enough Shared memory to meet the request.
显然，随着数据库服务器上物理内存的使用，高缓冲池命中率对于您的数据库性能而言始终比较好。
Obviously, with availability of physical memory on the database server, a high buffer pool hit ratio is always better for your database performance.
在这些分层解决方案中，有一个内存中的数据库缓存功能，作为后端数据库的前端。
An in-memory database caching capability ACTS as a front end to a back-end database in these tiered solutions.
另一个可选的方式是为测试使用内存数据库。
One alternative is to use an in-memory database for your tests.
因为实例共享内存的结束地址不固定，所以数据库共享内存的起始地址也是不固定的。
Since the end address of the instance Shared memory is not fixed, the starting address for the database Shared memory is not fixed either.
应用程序组内存集是从数据库共享内存集中分配的。
The application group memory set is allocated from the database Shared memory set.
应用程序共享内存：这是在应用程序连接到数据库时分配的内存，由处理连接到数据库的客户机所请求的工作的代理使用。
Application Shared memory: This refers to the memory allocated when an application connects to a database and is used by agents that do the work requested by the connected clients.
配置项可以是环境变量或者数据库配置修改，例如数据库的内存分配。
A configuration item may be an environment variable or a change in the database configuration, such as its memory allocation.
在不考虑数据库运行所需的额外硬件的情况下，数据库持久性的性能也好于内存到内存复制。
The performance of database persistence is also better than memory to memory replication, when not taking the extra hardware that the database is running on into account.
性能的限制因素是关于进入的数据量的并发数据库连接的数量和可用内存(RAM和磁盘)。
The constraining factors for performance are the number of concurrent database connections and available memory (both RAM and disk) in relation to incoming data volume.
数据库共享内存：这是数据库全局内存，是在激活数据库或者第一次连接到数据库时分配的。
Database Shared memory: This refers to the database global memory, which is allocated when the database is activated or connected to for the first time.
应用推荐