Memory Data Store,
or MDS, is a transactional in-memory
data store that can be used with SAS Federation Server.
The MDS driver supports most of
the FedSQL functionality. MDS
runs strictly in memory with no backup data store. Therefore, changes
are lost when the database is dropped or the server is restarted.
The database is created
in memory when the first user connects to the database. The database
remains in memory until one of the following conditions is met:
-
-
The data service or the catalog
associated with the data service is dropped.
Note: You cannot drop a MDS
data service or catalog if users are connected to the data service.
You can rename the database
and change the memory value while users are connected, but you cannot
drop the database while users are connected. To drop or rename a schema,
the table within the schema cannot be in use. Users can be connected
to the database, but they cannot have a table open in the schema.
Also, you cannot drop a table if it is referenced by a prepared statement
or has a pending transaction with uncommitted changes.
MDS supports optimistic
concurrency providing a serializable transaction, which means that
a transaction sees a consistent version of the data when the transaction
is started. When an MDS transaction starts, the state of the database
is logically frozen at that point in time. The transaction sees the
database consistently but changes made by other transactions are not
visible until the transaction is committed or rolled back, and its
state synchronized so that it sees the new state of the database.