Altering In-Memory and Relaxed Durability Databases

Keep these in mind when using alter database for in-memory and relaxed-durability databases.

  • You cannot set specify model, master or sybsystemdb as the template database.

  • Setting the database name in the use template claue to NULL removes the binding to any existing template database, and defines model as the template database.

  • Altering the template definition of a database that appears earlier in the database recovery order sequence than its template database automatically reorders the recovery order so the new template database appears prior to its dependent database in the database recovery order when you restart the server.

  • If you change the settings for durability or dml_logging, alter database automatically attempts to set the databases to single-user mode before executing the command. You can manually set the database to single-user mode before you issue alter table.

  • Databases must be in single-user mode before you can change the durability level setting.

  • You can increase the size of an in-memory database only on in-memory storage caches that already host the in-memory database.

  • You cannot change the durability level of system, template, or local temporary databases.

  • The load sequence is broken when you change the durability level of the database to full. For example, for a disk-resident database using full durability, if you:
    1. Dump a database.

    2. Perform a dump transaction.

    3. Perform a second dump transaction.

    4. Changed the durability to no_recovery.

    5. Changed the durability to full.

    You cannot perform a third dump transaction. Instead, you must perform a full dump database.