📌 Purpose & Quick Summary
Database maintenance, migrations, and backups are essential for web operations. BoostonCP provides 1-click database dump exports, web SQL import facilities, and automated table optimization tools. Whether you are restoring an existing database backup or preparing a staging copy, these tools allow high-speed execution without shell complexity.
🖥️ Interface Tour & Elements
- 1-Click SQL Export Button: Located in the Actions column of each database in the ledger, instantly downloading a compressed
.sql.gzdump. - Web SQL Import Tool: Dialog supporting drag-and-drop file upload of raw
.sqlor gzipped.sql.gzdump files. - Table Optimization & Repair: Integrated controls inside phpMyAdmin to check, repair, and optimize fragmented database tables.
- Purge Database Confirmation: Safety dialog with multi-step verification to prevent accidental data loss.
🛠️ Step-by-Step Instructions
Step 1: Exporting a Database Backup
- In the MySQL Databases view, locate the target database.
- In the Actions column, click the Export button (cloud download icon).
- The server generates a clean, transaction-safe mysqldump, compresses it with gzip, and downloads it directly to your browser (e.g.
user_dbname_backup.sql.gz).
Step 2: Importing a Database Dump
- Click the Import button in the database actions column or launch phpMyAdmin.
- If using phpMyAdmin:
- Select your target database from the left-hand tree.
- Click the Import tab in the top navigation.
- Click Choose File and select your
.sqlor.sql.gzfile. - Ensure the Character Set is set to
utf-8. - Click Import at the bottom of the page.
- A green notification confirms that all queries have executed and tables are restored.
Step 3: Decommissioning / Dropping a Database
- Locate the database in the ledger table.
- Click the Delete button (trash icon).
- Type the confirmation text prompted in the dialog to prevent accidental deletion.
- Click Confirm Purge. The database schema, all tables, and associated user grants are permanently removed.
⚙️ Complete Field & Parameter Reference Table
| Action / Feature | Supported Formats | Operational Impact |
|---|---|---|
| SQL Export | .sql.gz (Gzipped) |
Generates mysqldump with --single-transaction to prevent locking tables during export. |
| SQL Import | .sql, .gz, .zip |
Executes raw SQL statements sequentially within user memory limits. |
| Max Import Size | Up to 512MB |
Larger dumps should be uploaded via File Manager and imported via Web Terminal. |
| Purge Database | Permanent action | Irreversible deletion of all schema tables, rows, and assigned user privileges. |
❓ Troubleshooting & Common Errors
1. Import Fails with "MySQL server has gone away"
- Cause: The SQL dump contains a single table or query larger than the default
max_allowed_packet. - Solution: Split the SQL dump into smaller batches, or use the Web Terminal to import directly via command line:
mysql -u user_name -p user_dbname < backup.sql.
2. Import Fails with "Unknown Collation: utf8mb4_0900_ai_ci"
- Cause: The SQL dump was exported from MySQL 8.0 and is being imported into a MariaDB 10.x server.
- Solution: Open the
.sqlfile in the File Manager Monaco Editor, search forutf8mb4_0900_ai_ci, replace it withutf8mb4_unicode_ci, save, and re-import.