phpMyAdmin Import: How to Upload a Large SQL File

The errors you will see — limits and timeouts

Two limits bite — PHP's upload ceiling and script timeout — so the fixes go fastest-first:

1. Compress the dump — gzip the .sql to .sql.gz; phpMyAdmin decompresses on arrival, and a 10–20x shrink often clears the limit outright.
2. Bypass phpMyAdmin — cPanel Terminal or SSH: mysql -u user -p dbname < dump.sql handles hundreds of MB without PHP in the path.
3. BigDump.php — no SSH? This free script imports in chunks with automatic resume, straight from the browser.
4. Raise limits — cPanel → MultiPHP INI Editor: upload_max_filesize, post_max_size, max_execution_time — sensible when you administer the environment.
5. Packet errors — 'MySQL server has gone away' on huge INSERTs: max_allowed_packet needs raising on the server.

Verify row counts afterwards and repair oddities — the final section covers it. Database fundamentals sit in the cPanel MySQL database guide, and protecting what you import in the backup guide.

Fix 1 — compress the dump to .sql.gz

For “Fix 1 — compress the dump to .sql.gz”, change one thing at a time and reload in a private window. Note the exact error text, the URL, and what you changed last — that is what support needs. If the site was fine before an update or a DNS edit, undo that edit first. Email support@webji.services (24/7, Hindi and English) or open a ticket at https://billing.webji.in/submitticket.php?step=2&deptid=10. A 2 a.m. fault goes to email, not to the phone line.

Fix 2 — import via cPanel Terminal (mysql command)

Allow 80 and 443 to the world, and restrict SSH (22) or RDP (3389) to known IPs. A site that times out after a firewall change is usually a closed web port, not a dead server. If you lock yourself out, use the console in the client area or email support@webji.services before you reboot in a loop.

Fix 3 — BigDump.php for very large files

Pick the newest PHP version the site's plugins actually support, set it in the panel, and load the homepage plus one form. If the site whitescreens, switch back and read the error log before you try random plugins. Do not leave a shop on a PHP release that no longer gets security fixes.

Fix 4 — raise PHP limits (upload_max_filesize, max_execution_time)

How this plays out with max_execution_time: settings that look cosmetic usually decide page speed and uptime under real traffic. The defaults WebJi® ships are tuned for Indian network conditions, and support can review your setup on request.

Packet and timeout errors — max_allowed_packet

Two practical notes on mysql import command: it interacts directly with caching and database response, and misconfiguration is the most common cause of 'hosting is slow' tickets. WebJi® support checks it as part of standard migrations.

Verifying the import and repairing tables

Verification closes the job: check the row counts of your largest tables against the source (a SELECT COUNT on both ends takes seconds), confirm the site renders — no missing post types, no orphaned options — and run phpMyAdmin's Check Table on the tables the import touched.

If a table reports corruption, Repair Table fixes the common cases; a dump that fails validation gets re-imported, which is why the source dump stays on disk until verification passes. Note the final row count in your migration notes — future imports of the same database start from a known baseline instead of a guess.