# InnoDB Schema Changes

## MariaDB Enterprise Server InnoDB Schema Changes with the INPLACE Algorithm

Changes in enterprise databases and applications are inevitable. Schema changes often block other workloads, incur unique production situations that cannot be fully simulated for testing, and may have unpredictable execution times.

MariaDB Enterprise Server includes the In-place `ALTER` functionality for the InnoDB storage engine, such that:

When possible, schema change operations are performed `INPLACE`, minimizing impact on other workloads.

When the `alter_algorithm` system variable is set to `INPLACE`, schema change operations will not run unless they can be performed `INPLACE`, minimizing the risk of unpredictable behavior.

Additional information is available [here](/docs/server/server-usage/storage-engines/innodb/innodb-online-ddl/innodb-online-ddl-operations-with-the-inplace-alter-algorithm.md).

## MariaDB Enterprise Server InnoDB Schema Changes with the INSTANT Algorithm

Changes in enterprise databases and applications are inevitable. Schema changes often block other workloads, incur unique production situations that cannot be fully simulated for testing, and may have unpredictable execution times.

MariaDB Enterprise Server includes the Instant `ALTER` functionality for the InnoDB storage engine, such that:

When possible, schema change operations are performed `INSTANT`, minimizing impact on other workloads.

When the `alter_algorithm` system variable is set to `INSTANT`, schema change operations will not run unless they can be performed `INSTANT`, minimizing the risk of unpredictable behavior.

Additional information is available [here](/docs/server/server-usage/storage-engines/innodb/innodb-online-ddl/innodb-online-ddl-operations-with-the-instant-alter-algorithm.md).

## MariaDB Enterprise Server InnoDB Schema Changes with the NOCOPY Algorithm

Changes in enterprise databases and applications are inevitable. Schema changes often block other workloads, incur unique production situations that cannot be fully simulated for testing, and may have unpredictable execution times.

MariaDB Enterprise Server includes the No-copy `ALTER` functionality for the InnoDB storage engine, such that:

When possible, schema change operations are performed `NOCOPY`, minimizing impact on other workloads.

When the alter\_algorithm system variable is set to `NOCOPY`, schema change operations will not run unless they can be performed `NOCOPY`, minimizing the risk of unpredictable behavior.

Additional information is available [here](/docs/server/server-usage/storage-engines/innodb/innodb-online-ddl/innodb-online-ddl-operations-with-the-nocopy-alter-algorithm.md).

<sub>*This page is: Copyright © 2025 MariaDB. All rights reserved.*</sub>

{% @marketo/form formId="4316" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://mariadb.com/docs/server/server-usage/storage-engines/innodb/mariadb-enterprise-server-innodb-operations/schema-changes/schema-changes-innodb-schema-changes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.