How to Change MariaDB Settings

Required permissions

Use the database project ID as project-id and grant only the scope for the requested action:

Action	Minimum scope
View the project	`project.read` on `project:<project-id>`
Change the name	`project.name.update` on `project:<project-id>`
Change the description	`project.description.update` on `project:<project-id>`
Change the password	`database.password.rotate` on `database:<project-id>`
Change the version	`database.version.update` on `database:<project-id>`
View the connection	`database.connection.read` on `database:<project-id>`

An owner has full access in a user session. assistant, member, and organization API Keys need the specific grant. The linked-applications lookup currently uses database.password.rotate in the API contract.

Accessing the Settings

In the sidebar menu, click Projects
Find and click the desired database project name
On the project page, click the "Edit" button in the top-right corner

Available Settings

Project Name

The project name can be changed at any time.

Rules:

Minimum: 6 characters
Maximum: 32 characters
Only lowercase letters, numbers, and hyphens

Note: Changing the name does not affect the connection address, which uses the project ID.

Project Description

The project description can be changed at any time.

Characteristics:

Optional field to describe the project purpose
Helps identify and organize your projects
Can include information such as environment, customer, or purpose

Database Password

You can renew the password of the app user at any time. You do not choose the new password: Zenifra generates a completely new one.

How to change it:

In the password section, request a new password
Confirm the action
Copy the new password shown and store it safely; it is shown only once

Warning: The database may be unavailable during the process.

Important: Linked applications are not updated automatically. The console lists those applications; manually update the connection variable (for example, DATABASE_URL) in each one.

MariaDB Version

The MariaDB version can be updated.

Available versions:

MariaDB 10
MariaDB 11

The console only offers versions newer than the current one.

How to update:

Select the desired new version
Click Save

Warning: Version upgrades can cause a few minutes of downtime. We recommend making the change during low-traffic hours.

Important: MariaDB version downgrade is not supported. Export your data with mariadb-dump/mysqldump before upgrading and test the application with the new version.

Connection String

The connection string is generated automatically and can be viewed at any time, with the password masked.

Format:

mariadb://app:<password>@mariadb-<project-id>.managed.zenifra.com:<port>/app?ssl=true

The connection requires TLS and points to the primary instance.

To copy: Click the copy button next to the connection string.

Tip: Use this string in your HTTP application's DATABASE_URL variable to connect to the database.

Replicas (MariaDB)

MariaDB on Zenifra uses a fixed configuration of 3 instances:

1 primary instance: receives write and read connections
2 replicas: keep a copy of the data and can take over if the primary fails

Note: Unlike PostgreSQL, MariaDB replica count is fixed (3 instances) and cannot be changed.

Automatic Failover

MariaDB includes automatic failover:

if the primary instance fails, one of the replicas can be promoted automatically
the connection keeps the same host and port
open connections can be closed during the switch; configure your application to reconnect automatically

Storage

Database storage can be adjusted.

Limits:

Minimum: 1 GB
Maximum: 250 GB

Impact:

For hourly projects: storage can be increased
For monthly/yearly contracts: storage is set at purchase and cannot be changed during the contract

Plan

In hourly billing, you can change the database plan in the project edit page. On monthly or yearly contracts, the plan cannot be changed during the contract. The change may cause temporary downtime.

Automatic renewal

On monthly and yearly contracts, the project edit page lets you enable or disable automatic contract renewal.

Warning: Storage reduction is not supported. Increasing storage can cause a few minutes of downtime.

Project Actions

Stop the Project

When stopping the project:

the database is interrupted
replicas are shut down
the project becomes inaccessible
for hourly projects, plan billing stops, but storage costs continue

When to use it:

when you do not need the database temporarily
to save money on hourly projects

Start the Project

To start a stopped project:

the database starts again
replicas are initialized
the project becomes accessible again
for hourly projects, billing resumes

Delete the Project

Deletion is permanent and irreversible.

What happens:

all replicas are removed
all data is deleted

Warning: Zenifra does not keep database backups. Export your data with mariadb-dump/mysqldump before deleting. This action cannot be undone.

Next Steps

FAQ

Can I change the database password?

Yes. At any time through the project settings; Zenifra generates the new password and shows it only once. Remember to update the connection variable in the applications that use the database.

Does changing settings cause downtime?

It depends on the change:

Password: May cause downtime during the process
MariaDB version: May cause a few minutes of downtime
Replicas: Fixed configuration (not changeable)
Storage: May cause a few minutes of downtime
Plan: May cause temporary downtime

Can I restore a deleted database?

No. Deletion is permanent and there is no platform backup. The data cannot be recovered. Export your data before deleting.

What happens if the primary instance fails?