Typically when using phpmyadmin, there is more than one way to copy a database to another database on the same server. For starters, you don't want to modify the live database because it could disable your store and again that would defeat the purpose of this whole process.
One way is to export the database and in that process it is or should be possible to identify which table(s) to include. Another and I apologize for not remembering the exact process, but there is typically an option to copy the database from one to another when you are able to see the list(s) of databases. That option tends to not be limited to the size of the existing database.
Next is to identify what is causing the excessive database size and possibly address that. Also to identify how many tables are present. A typical ZC install has approximately 100 tables. Any multiple of that number indicates the number of "stores" have been attempted to be installed to the database.
The prefix zen_ indicates that at one time or currently an includes/configure.php file had a line similar to:
Code:
define('DB_PREFIX', 'zen_');
If your current live store has something on the right side of that function, then database tables that begin with that "phrase" should be included in your export/copy. If the right side is just two single quotes ('') then tables that do not include a prefix are the ones to be copied and others with a prefix should be ignored.
So as said, even if the database is large it could be exported in parts by selecting the desired table(s) as necessary to keep the file size small enough to transfer. Also, it may be possible to transfer as a zip or gzip file which will compress the overall size.
These are all factors of consideration and working around system constraints. At worst you may have to ask your host to perform the copy as they have the possibility of accessing more of the system.
Bookmarks