In-memory and Relaxed-Durability Databases

Replication Server supports the in-memory and relaxed-durability database Adaptive Server feature.

In-memory databases (IMDB) reside entirely in cache and do not use disk storage for data or logs, and therefore do not require disk I/O. This results in potentially greater performance than a traditional disk-resident database (DRDB), amongst other advantages. Since an in-memory database exists only in cache, you cannot recover the database if the supporting host is shut down or the database fails.

With relaxed-durability databases, Adaptive Server extends the performance benefits of an in-memory database to disk-resident databases. Disk-resident databases perform writes to disk, and ensure that the transactional properties of atomicity, consistency, integrity, and durability, known as the ACID properties, are maintained. A traditional disk-resident database operates at full durability to guarantee transactional recovery from a server failure. Relaxed-durability databases trade the full durability of committed transactions for enhanced runtime performance for transactional workloads. A relaxed-durability database created with the no_recovery level is similar to an in-memory database: you cannot recover data or logs if the server terminates or is shut down. You can also create a relaxed-durability database with the at_shutdown level where transactions are written to disk if there is a proper shut down of the database.

See Adaptive Server Enterprise In-Memory Database Users Guide.

Replication Server Support

Replication Server supports as the primary and replicate database:

  • In-memory databases

  • Relaxed-durability databases set with durability at no_recovery

For convenience, relaxed-durability databases refers to relaxed-durability databases with durability set to no_recovery.

You can initialize an in-memory and a relaxed-durability database as a new primary or replicate database by obtaining data, object schema, and configuration information from one of:

  • A template database that retains basic information.

  • A database dump from another database and then load the dump to the target in-memory database or relaxed-durability database.

The dump source database can be another in-memory database, relaxed durability database, or a traditional disk-resident database.

Note: Replicating to or from an in-memory database may not be faster than replicating to or from a relaxed durability database. DML on in-memory databases depends on several factors.

In addition, there is no difference in performance when replicating to or from an in-memory or relaxed durability database compared to replication between primary and replicate databases which are traditional full durability disk-resident databases.