Skip to main content
.com domains from $2.99 — free WHOIS privacy on every name

Database tooling · Intermediate · 20 minutes to learn

How to use phpmyadmin — Export First, Then Touch Anything

You are one missing WHERE clause away from rewriting every row in a table, and the only thing standing in the way is an export you have not taken.

The short answer

The rule that makes phpMyAdmin safe is one click: take an Export before you change anything. Reading is free and alters nothing, so the risk in this tool lives entirely in the SQL tab and the edit form, and an export turns any mistake there into a file you already hold.

The second rule is to run the SELECT before the UPDATE. Same WHERE clause, read the row count, and only then convert it to a write. A statement without a WHERE succeeds instantly across every row in the table, and instantly is the operative word.

By the HostingFast team · Reviewed 24 August 2026

Intermediate

Difficulty grade

Quick

Time budget

5

Stages

24/7

Engineer cover

Written for somebody who can read a table and is nervous about writing to one, which is the correct instinct. It covers what each pane does, what an export contains, and the two places the tool will happily let you cause damage.

There is a section on serialised data because that is the specific trap in WordPress databases, and a naive find-replace corrupts it in a way that is not obvious until something stops loading.

What each pane is for

The left column lists databases and their tables with row counts. Browse shows the rows; Structure shows the columns, types, keys and indexes. Neither changes anything, so orientation is free and should come before every session rather than only the first.

Structure is also where you find out whether a slow query has an index to work with. A table scan on a hundred thousand rows and an indexed lookup on the same table are different orders of magnitude, and the index list tells you which one you are getting.

The export is the undo button

The Export tab produces a complete SQL dump — schema and data — in seconds, with gzip available for anything large. Check the routines and triggers options if the database has any, because the quick export omits them and their absence is not obvious until something fails.

Take one per session, not per week. The habit costs a click and converts every subsequent mistake from an incident into an import. This is the single most valuable thing on the page.

SQL you can run, and SQL you should not

UPDATE and DELETE without a WHERE clause apply to every row and commit immediately. The discipline is to write the statement as a SELECT with the identical WHERE, read the row count, and only then swap the verb — if the count is not what you expected, the clause is wrong.

Add LIMIT while testing. On InnoDB tables you can wrap changes in a transaction and roll back, but phpMyAdmin runs each submission in its own session by default, so treat the export as the real safety net rather than relying on transactional behaviour you have not configured.

Serialised data, imports, and the upload ceiling

PHP serialised strings record the byte length of every value they contain. Replace a URL with a longer or shorter one using a plain find-replace and the recorded lengths no longer match, so the option unserialises to nothing and whatever depended on it quietly stops working.

For WordPress URL changes, run wp search-replace over SSH: it deserialises, replaces and reserialises correctly. And note the import ceiling — upload_max_filesize and post_max_size bound what phpMyAdmin will accept, so a large restore goes over SSH with the mysql client instead.

Driving a hosting account through the cPanel dashboard

The platform these operations were run on

Every tab and setting described here was exercised on the stack we operate: the panel's own phpMyAdmin, the same MySQL service, the same PHP limits. The interface in the guide is the interface in your account.

The rate you sign up at is the rate you renew at, so the second year costs exactly what the first did and the line in your accounts stays a fixed number.

  • Export before every session
  • SELECT before UPDATE, always
  • Serialised data handled properly
  • Engineers on shift at any hour

Why HostingFast

Standard on every plan

Reading costs nothing

Browse and Structure change nothing at all, so orientation is free and comes first every time.

The export is the undo

One click before every session, and a mistake becomes a file you are already holding.

SELECT before UPDATE

Run the WHERE clause as a read and check the row count before anything gets written.

Serialised data explained

Why a plain find-replace corrupts WordPress options, and what to run instead of it.

Import limits named

upload_max_filesize and post_max_size are the ceiling, and SSH is the way past it.

Indexes visible in Structure

The same screen that shows your columns tells you whether a slow query has an index to use.

Quick Start

From order to online

  1. 1

    Open Browse and Structure and read

    Row counts, column types, keys and indexes. Nothing here writes, and knowing the shape of the table prevents most of what follows going wrong.

  2. 2

    Export the database before you change anything

    Full SQL dump, gzipped if it is large, routines and triggers included if the database has them. One click, every session.

  3. 3

    Run the SELECT before the UPDATE

    Identical WHERE clause, read the row count. If the number surprises you, the clause is wrong and you have just avoided rewriting a table.

  4. 4

    Use the edit form for single-row changes

    Browse, then the pencil icon, then the field. For one setting or one address that is safer than hand-written SQL and takes less time.

  5. 5

    Restore by Import, or over SSH when the file is large

    Import replays a dump. Past the PHP upload limits, use the mysql client over SSH instead of splitting the file.

Built In

Loaded onto every plan

  • SSH, Git and Composer on the developer-focused plans
  • NVMe SSD storage on every tier, not just the expensive ones
  • Daily backups with restores you trigger yourself from the panel
  • Staging environments for testing before anything ships
  • PHP version set per site from the panel, not per server
  • LiteSpeed caching in the server itself, not bolted on by plugin
  • cPanel — the panel most of the industry already automates against
  • 99.9% uptime as the target, monitored around the clock
  • Renewal billed at the rate you first signed up at
  • Engineers on shift every hour of every day, not a queue that opens at nine

Frequently Asked

What people ask us most often

How do I change a URL across a WordPress database safely?

Not with find-replace in phpMyAdmin. Serialised option values carry the byte length of each string, so replacing text of a different length breaks them and the data unserialises to nothing. Run wp search-replace over SSH, which deserialises and rebuilds the values correctly, and take an export first either way.

My import fails on a large SQL file — what is the limit?

phpMyAdmin uploads through PHP, so upload_max_filesize and post_max_size cap it, and the execution timeout can end a long import midway. Gzip helps a little. Past that, use the mysql client over SSH: it streams the file with no web-server limits involved and tells you exactly which statement failed if one does.

How many sites can one account carry?

From the Turbo tier up, yes — multiple sites, each with its own domain, mailboxes and certificate, all inside a single account. If the extra sites belong to clients rather than you, look at reseller hosting instead: it keeps each one properly walled off.

What is the refund window, and what falls outside it?

Thirty days on shared, business, WordPress and WooCommerce hosting; seven on reseller. VPS and dedicated servers are provisioned to order the moment payment lands, so they fall outside the guarantee — the same goes for domain registrations, where the registry charges the instant the name is secured. Within the window, one request gets your hosting fee back — no retention gauntlet to fight through.

Keep reading

Changing hosts? Run through our checklist first.

A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.

You'll get the checklist email, then occasional pointers on keeping a site running fast. Unsubscribe the moment you want out — the privacy policy covers the rest.

Query it on faster disks.

NVMe storage, LiteSpeed in the server itself, free SSL and free migration, and engineers on shift at any hour.

View VPS Hosting plans