Creating In-Memory and Relaxed Durability Databases

The database_device you list for the in-memory database must be an in-memory storage device.

The for load parameter indicates that the database is created initially in a state waiting to be loaded using a load database command.

You cannot:

Create an in-memory database on a default device.
Use in-memory databases for system databases (other than tempdb).
Use an in-memory database as an archive database. You should not use an in-memory database as a scratch database.
Use the same name for the database you are creating and its template database.
Specify system databases, including model, as the template database.
Mix disk-based and cache-based storage devices. The SAP ASE server treats databases created entirely on in-memory storage cache as in-memory databases. You cannot use:
- In-memory storage devices created on different in-memory storage caches for one in-memory database
- In-memory storage devices created on one in-memory storage cache, either in full or in part, for different in-memory databases
Use the use as template parameter with the with default_location = parameter.
Use the for load and for proxy update parameters with the use as template parameter.

You can:

Create in-memory databases on in-memory storage devices residing on named caches as long as all the in-memory storage devices are hosted by in-memory storage cache.
Create mixed log-and-data in-memory databases on the same in-memory storage devices. However, mixed log-and-data in-memory databases must be on a single cache.

The durability = no_recovery parameter is required when you create an an in-memory database. This parameter reinforces the behaviour that in-memory databases are always recreated when you restart the server.

SAP ASE includes a 30-day trial period, during which you can try the in-memory database feature. However, if you use this feature, at the end of the trial period, you must:

Purchase an in-memory license, or
Purchase an SAP ASE license that does not include the in-memory feature. In this case, you must drop and recreate the user-defined temporary databases without using the explicit durability parameter.