Databases & MySQL

It depends on your plan, and the number is shown in your control panel rather than fixed across every account.

A scheduled export you never have to remember to run is worth more than the best manual backup habit.

Changing the database default does not touch existing tables, which is the part that catches people out.

Your control panel and phpMyAdmin both show it directly, and a short query breaks it down table by table.

Every MySQL connection, in any language, comes down to the same four values — here is where to find them and how to use them.

Every application needs a database, a user, and that user attached to the database — here is the order to do it in.

Three checks before you delete a database, because there is nothing to undo it with afterwards.

Turn a live database into a single portable SQL file, ready to back up, move, or hand to a developer.

A slow site is usually a slow query wearing a disguise — here is how to catch it in the act.

The database name your application is asking for does not exist, at least not under that exact name, on that server.

The database has a limit on simultaneous connections, and something is holding on to more of them than it should.

A database user with no privileges cannot do anything, and one with too many is a risk you do not need to take.

A file too big for a browser upload still has three practical ways in — compression, splitting, or the command line.

Point phpMyAdmin at a SQL file and it rebuilds the database from it — provided the file is small enough for a single upload.

An export, a transfer, an import, and a small set of connection details to update once it lands.

OPTIMIZE TABLE reclaims space and refreshes statistics — but it behaves differently depending on the storage engine underneath.

A corrupted table has a specific fix, and it is different depending on whether the table is MyISAM or InnoDB.

Resetting the password is the easy part — updating every application that still has the old one saved is the part people forget.

A plain find-and-replace can silently corrupt serialized data — here is how to do it without breaking the site.

Two databases that speak the same SQL and the same connection protocol, with a history and a licensing model that pulled them apart.

A short string in front of every table name, mainly so more than one application can share the same database.

MySQL called something utf8 that was not quite real UTF-8, and utf8mb4 is the character set that actually is.

A decades-old vulnerability that still appears in new code, and the small set of habits that reliably prevent it.

It means "this same machine" — not a placeholder, and not something to change unless you actually need to.