> ## Documentation Index
> Fetch the complete documentation index at: https://artie.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# MariaDB

> Learn how to configure MariaDB as a destination in Artie through the MySQL destination, including service account creation, supported versions, and how JSON columns are stored.

Artie writes to MariaDB with its MySQL destination. Select **MySQL** as the destination in the Artie dashboard and enter your MariaDB connection details. There is nothing MariaDB-specific to configure.

## Required settings

* Host name
* Port (default is `3306`)
* Service account

### Creating a service account

```sql theme={null}
CREATE USER 'artie' IDENTIFIED BY 'password';

-- Allows Artie to merge data, create and alter destination tables, and clean up
-- its temporary tables.
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, ALTER ON *.* TO 'artie';
```

## Destination database routing

Like MySQL, MariaDB treats schemas and databases as the same thing. Routing to one database or to multiple databases works exactly as described in [MySQL destination database routing](/docs/destinations/mysql#destination-database-routing), including the database-scoped grants.

## MariaDB differences

### JSON columns are stored as `LONGTEXT`

Artie creates JSON columns for source JSON, struct, and array values. In MariaDB, `JSON` is an alias for `LONGTEXT` with a `json_valid` check constraint, so `SHOW CREATE TABLE` and `INFORMATION_SCHEMA.COLUMNS` show these columns as `longtext`. Artie still recognizes them as JSON columns, and MariaDB's JSON functions such as `JSON_EXTRACT` work on them as usual.

## FAQ

### Which MariaDB versions are supported?

Artie supports MariaDB 10.6, 10.11, and 11 or higher.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.