> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/server/architecture/server-constraints.md).

# Server Constraints

{% columns %}
{% column %}
{% content-ref url="/pages/5TBe9CxJOF9ArTGcFRQN" %}
[Server Constraints Overview](/docs/server/architecture/server-constraints/server-constraints-overview.md)
{% endcontent-ref %}
{% endcolumn %}

{% column %}
Provides a high-level overview of how MariaDB Server enforces data integrity through various architectural constraint types.
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}
{% content-ref url="/pages/cFxjWF5fTZLP1SZzW8SQ" %}
[AUTO\_INCREMENT Constraints](/docs/server/architecture/server-constraints/auto_increment-constraints.md)
{% endcontent-ref %}
{% endcolumn %}

{% column %}
Explains the limitations and behavior of `AUTO_INCREMENT` columns, including how they handle maximum values and gaps in sequences.
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}
{% content-ref url="/pages/frdXkOf4PaYrzWTccOmR" %}
[FOREIGN KEY Constraints](/docs/server/architecture/server-constraints/foreign-key-constraints.md)
{% endcontent-ref %}
{% endcolumn %}

{% column %}
Details the requirements and limitations for defining foreign keys to ensure referential integrity between tables.
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}
{% content-ref url="/pages/JQVhrdu6QF8M04rjsgFn" %}
[NOT NULL Constraints](/docs/server/architecture/server-constraints/not-null-constraints.md)
{% endcontent-ref %}
{% endcolumn %}

{% column %}
Describes how `NOT NULL` constraints prevent `NULL` values from being stored in specific columns.
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}
{% content-ref url="/pages/T1jDxKqBqLYEn4pyiOmd" %}
[PRIMARY KEY Constraints](/docs/server/architecture/server-constraints/primary-key-constraints.md)
{% endcontent-ref %}
{% endcolumn %}

{% column %}
Outlines the rules for primary keys, which uniquely identify each record in a table and cannot contain `NULL` values.
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}
{% content-ref url="/pages/UfoCAjXIfk1NNMljj61A" %}
[UNIQUE Constraints](/docs/server/architecture/server-constraints/unique-constraints-with-mariadb-enterprise-server.md)
{% endcontent-ref %}
{% endcolumn %}

{% column %}
Explains the specific implementation and considerations for unique constraints when using MariaDB Enterprise Server.
{% endcolumn %}
{% endcolumns %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://mariadb.com/docs/server/architecture/server-constraints.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.