Limits for in-memory and relaxed-durability databases

In-memory and relaxed-durability databases include these limits:

The Cluster Edition does not currently support in-memory databases, relaxed-durability databases, template databases, or minimally-logged DML.
Replication Server does not currently support replication of in-memory databases, or databases with durability set to no_recovery.
You cannot use an in-menory database as an archive database.Sybase reommends that you do not use an in-memory database as a scratch database.
In-memory databases do not support queries using compatibility mode. Use compatibility mode in Adaptive Server only on regular disk-resident database tables. See the Migration Technology Guide about enabling compatibility mode.

If you have enabled compatibility mode and a query touches a table in an in-memory database, Adaptive Server reverts to the native version 15.0 query optimizer and execution engine using the “restricted compatibility mode.” Generally, this mode produces query plans similar to the plans in Adaptive Server version 12.5. If you notice a degradation in performance, Sybase recommends that you disable compatibility mode for this query.
You cannot change the durability or logging level of in-memory or low-durability databases in the same command in which you are increasing the size of the database.
alter database, when used to change either the durability or minimal_logging attribute of the database, automatically puts a database into single-user mode, and the command fails if it cannot acquire exclusive access to the database. To avoid this failure, manually put the database in single-user mode before running alter database.
In-memory and relaxed-durability databases cannot participate in distributed transactions.
In-memory and relaxed-durability databases cannot coordinate multidatabase transactions involving databases with full durability. When you execute system procedures that perform transactional updates when you run a stored procedure from an in-memory or relaxed-durability database, you see this error:
```
Msg 3952, Level 16, State 2:
Procedure 'sp_XX', Line 258:
Command not allowed. You cannot start a multidatabase operation in database 'master'
after starting the master transaction in 'imdb1' as it may render the database 'master' unrecoverable. 
```
To run the system procedure:
1. Execute it from a fully durable database. For example, to run sp_XX in master, enter:
```
use master
go
exec sp_XX
```
2. Use this formate to reference the stored procedure from the current database (in-memory or relaxed-durability): database_name.owner.sp_name.
  
  For example, to run sp_XX in the imdb_1 in-memory database, enter:
```
use imdb_1
go
exec master.dbo.sp_XX
```
From an in-memory database, you cannot use a proxy table or database to map to another in-memory database or disk-resident database object.
From a disk-resident database, you cannot use a proxy table or database to map to an in-memory database or table.