A site on a small VPS
The database restarts during traffic peaks. The health check reports memory warnings, and LayerAssist tunes the settings to fit the server.
Keep the database behind your website healthy.
Everything your site shows lives in its database. LayerAssist checks that it’s running and reachable, looks for errors and slow queries, and explains problems before they take your site down.
At a glance
- AutomationThe ready-made “Database health” automation checks that the database is running and reachable, and reports errors or slow queries it finds in the logs.
- Built-in monitorFor an alert the moment the database stops, add the built-in service monitor for your database service.
- In chatIn chat, it fixes connection errors, repairs damaged tables and finds what makes the database slow.
When the database fails, the whole site goes blank
Your pages, products, orders and users all live in a database, usually MySQL or MariaDB. If the site can’t reach it, visitors see “Error establishing a database connection” or an empty page, and nothing works until it’s fixed.
Databases also wear down slowly: tables get damaged after a crash, queries slow down as data grows, and the server runs short of memory. These problems leave warnings in the logs long before they take the site down.
Signs your database needs attention
- “Error establishing a database connection”
- Pages that used to be fast now take seconds
- “Table is marked as crashed and should be repaired”
- Admin pages time out while saving
Common database problems
Wrong connection details
A password, user or host changed in the hosting panel but not in the site’s settings breaks the connection instantly.
The database service stopped
Lack of memory, a full disk or a failed update can stop MySQL or MariaDB.
Damaged tables
A crash, or a full disk in the middle of a write, can damage a table so that some pages fail.
Slow queries and bloat
Tables that grow without limit — logs, sessions, revisions, expired data — make every page slower.
How LayerAssist looks after your database
It checks the database the way a database administrator would, and explains it the way a friend would.
Checks it’s up and reachable
It verifies that the database service is running and that your site can connect to it.
Reads the warnings
It looks through the database’s logs for errors, damaged tables and slow queries, and reports what’s new.
Repairs what’s broken
In chat it corrects connection settings, repairs damaged tables and clears out data your site no longer needs, deleting only with your OK.
Finds what’s slow
It looks at the largest tables and the slowest queries and tells you what would make the biggest difference.
Example: a shop admin that got slower every month
What it checks
- MariaDB: running and reachable
- Sessions table: 2.1 million expired rows, 3.4 GB
- Slow query log: order searches read the whole table
- Damaged tables: none
What it changes
Cleared the expired sessions after your OK and added the missing index for order searches
What you get
- Early warnings from the logs, before the site goes blank
- Connection errors fixed in minutes, with the cause explained
- A faster site from a cleaner database
- Your content stays put: deletions only with your OK
Real situations
A busy WooCommerce shop
Orders and logs grow every day. A daily health check flags the fastest-growing table before it slows the shop down.
A developer’s app on PostgreSQL
After a release, the app’s database logs slow queries. The hourly check on the Pro plan points them out the same day.
How to set up database health checks
Connect your hosting or server
SSH gives the fullest picture; a hosting panel works for many shared-hosting sites.
Add the automation
In Automations, choose New automation, pick the site and select “Database health”.
Choose how often
From once a day up to every 15 minutes, depending on your plan.
Add the service monitor too
For an instant alert when the database stops, add a “Service health” monitor for mysql or mariadb on the same server.
Questions about database health
Mostly MySQL and MariaDB, which nearly every website uses. With SSH it can also work with PostgreSQL and other databases your server runs.
Yes. In chat it checks which tables are damaged, repairs them and confirms your pages load again.
No. The ready-made automation only checks and reports. Changes happen in chat, and deleting data always needs your OK.
The service monitor is a quick check without AI that the database is running, and it alerts at once. The health check is an AI review of its logs and performance on your plan’s schedule. They work well together.
Related guides
- Built-in monitorServer servicesAlerts you when a service like your database stops.
- In chatWebsite speedMeasures load times, finds what slows your site and fixes it.
- Built-in monitorDisk spaceWarns before a server disk fills up, and frees space safely.
All monitoring guidesSee what each plan includesHow LayerAssist works
From $9 a month · 14 days to change your mind
Next time something breaks, you’ll know who to ask.
Add your website and ask your first question today. Not for you? Cancel within 14 days to get your first payment back, minus only the AI work you used.
Free for 7 days · No credit card needed · No technical knowledge needed.