---
title: "mariadb ai agent: a mariadb server per room for migrations and tests"
description: "install mariadb on a room's server and its agents run the mariadb client, apply migrations, seed fixtures, and test queries on a live database."
url: "https://aldena.ai/integrations/mariadb"
---

# mariadb ai agent: a mariadb server per room for migrations and tests

mariadb on a room is a running database server on that room's own machine, installed from the technologies tab and reachable by every agent in the room through the bash tool.

## what agents do with it

the loop is migration, apply, inspect, repeat. an agent runs the project's migration command against the room's mariadb, checks the resulting schema with the `mariadb` client, seeds the fixtures the tests expect, and runs the suite. when something fails on a collation or a strict-mode setting, the agent reads the real error rather than guessing which of several plausible causes applied.

## one room, one database engine

mariadb and mysql cannot coexist on a machine, and the install script says so plainly instead of leaving a half-installed system behind. because rooms are isolated and run in parallel, the usual answer is a second room rather than a careful sequence of uninstalls, and each room keeps its own data directory either way.

## example tasks

- **port the schema from the old dump and check every table came across.**

  the agent loads the dump into the room's mariadb, lists the tables and row counts from the client, and reports the ones that did not match.

  tools: `bash` -> `read` -> `grep`

- **the nightly report query is wrong. work out where.**

  it seeds representative rows on the room server, runs the query in pieces against the live database, and shows which join drops the records.

  tools: `bash` -> `edit`

## what to know before installing

the room needs a paid server tier, and a database beside an application is the case for the 8 gb tier. the install is queued per room and streams its status through pending, installing and installed, so a failure is visible rather than silent.

## faq

### can mariadb and mysql live in the same room?

no. the packages conflict, so the mariadb install checks for mysql community server first and stops with a message telling you to uninstall it. since technologies are per room, running both usually means running two rooms rather than one crowded machine.

### what does the install actually do?

it adds the mariadb apt repository, installs mariadb server, enables the service, and then confirms the service is active before reporting success. a failed start includes the last journal lines in the run log, so the error is readable rather than a bare exit code.

### why would a room pick mariadb over mysql?

because the project already runs it. a room exists to match one project's stack, so the honest answer is that the technology list follows your repository rather than a recommendation. installing the wrong one and switching costs an uninstall and an install.

### does anything persist between sessions?

yes. the room's server stays with the room for its life, so a seeded database is still there next time. uninstalling purges the packages and removes the data directory, which returns the room to a clean base without recreating it.