# Supported database engines in Managed ClickHouse®

A database engine controls how a database manages tables and metadata.
It determines what happens when you list, create, or delete tables and can
restrict a database to specific table engines or manage replication.

This differs from [table engines](/product/dbaas/service-specific/clickhouse/reference/supported-table-engines/),
which determine how data is stored on disk or read from external sources and
exposed as virtual tables.

Managed ClickHouse® supports different database engines depending on the
service version. Engine availability can differ from upstream depending on
features enabled in Managed ClickHouse®.

> [!IMPORTANT]
> Databases you create with SQL always use the `Replicated` engine: a `CREATE DATABASE`
> statement with any other `ENGINE` clause is rejected with `Code: 497 ... Only Replicated
> database can be created through SQL`. The engines below are the ones the service exposes,
> for example for databases created by the platform, and they determine how existing
> databases behave.

For details about each engine, see the
[ClickHouse database engines documentation](https://clickhouse.com/docs/reference/engines/database-engines).

## Supported database engines

| Engine | Supported in |
| ------ | ------------ |
| `Atomic` | 25.3, 25.8 |
| `Lazy` | 25.3, 25.8 |
| `MaterializedPostgreSQL` | 25.3, 25.8 |
| `Memory` | 25.3, 25.8 |
| `MySQL` | 25.3, 25.8 |
| `Ordinary` | 25.3, 25.8 |
| `PostgreSQL` | 25.3, 25.8 |
| `Replicated` | 25.3, 25.8 |