It is recommended that you use the cPanel interface for any database export/import.

In addition, a warn on the export/import tabs stating a similar situation + validate checkbox 'Full import or import database creation from the PHPMyAdmin interface could cause discrepancies within the cPanel database handler, resulting in server backup failures. Although this operation is not directly supported by MySQL, phpMyAdmin does it indirectly by creating a new. Check 'I Understand the Risk' to continue.' A Rename database to dialog is available. Please drop/rename via the cPanel interface instead. Wouldn't it be less volatile if that option were removed? Or if not removed, how about a nice fat warn + validate checkbox 'renaming or deleting databases from the PHPMyAdmin interface could corrupt the cPanel database handler, resulting in server backup failures. Renaming the DB via PMA means that cPanel won't find it (since it still thinks its the old name). While using PMA in domain/account level cPanel however, a user still has the option to 'rename database' under Operations. Rename it via the phpmyadmin backend UI (preferable): Or just execute this SQL (only use it if the database is fresh and does not contain any data yet, otherwise it will be lost) CREATE DATABASE newname DROP DATABASE oldname Share. If database schema inconsistency is causing such an issue with backup corruption, why are those features even allowed in PMA? For example, there is no way to manage users in the cPanel build of PMA, the tab is completely gone, I assume in order to prevent collisions with the cPanel DB system/API. I am curious about this: Why are we letting 1 user take down a whole server with settings that are known to conflict? PMA is an excellent and dare I say essential tool for many users, but if it's so easy to conflict with cPanel - risky to allow. I just ran into the backup failure again this morning due to a database being renamed in PHPMyAdmin (PMA). The left side of the main screen of phpMyAdmin is where you will find your database listed, with the table listed below the database name. When you press the continue button, you’ll notice that your old name has been replaced with a. After clicking on the Rename, you’ll be redirected to a screen where you can choose a New name, Click the Proceed button after entering the new name. Thanks for adding that protection in v64. Change the name of the Database by clicking on it.

Phpmyadmin rename database