An SQL export saves database structure and data in a form that can be restored later. Download it before a database edit, migration or application upgrade, and store it securely because it can contain personal records and application secrets.
IN THIS ARTICLE
What you need before you begin
Identify the database from the application’s configuration and confirm you have access to every required table. For a busy transactional application, use its supported maintenance or consistent-backup approach so related records are captured coherently.
01 Export a recoverable database backup in phpMyAdmin
- Open phpMyAdmin and select the intended database. Review its table names to confirm it belongs to the correct application.
- Choose Export and select SQL. A quick export suits a straightforward full database copy; use Custom when you need to inspect table selection and options.
- Include both structure and data for a full recovery copy. Include relevant triggers, routines or events only when the application uses them and your export permissions support them.
- Download the file, using supported compression for a large export if helpful. Record the database name, application version and creation time separately.
- Check that the file is nonempty and readable, then test restoration into an isolated database when the backup will support a significant change.
Check the backup or recovered data
A useful backup can recreate the expected tables and representative records. Verify important text encoding and any required objects rather than relying on filename or archive size alone.
What if the database export fails, and does it include website files?
If export fails or times out, use a supported server-side backup method or contact support. A database export does not include website uploads, configuration files or mailboxes. Keep the matching website backup when planning a full application recovery.