phpMyAdmin Database Import Export issue

Error
It is possible that you found a bug in the SQL Analyzer. Please check your query carefully, including whether the quotes are correct and match. Other possible reasons for failure may be because you have uploaded binary data beyond the reference text area. You can also try your query at the MySQL command line interface. If possible, the error output from the MySQL server is listed below, which may help you solve the problem. If you still have a problem, or if the command-line interface succeeds and the parser fails, reduce your SQL query to one of the statements that caused the problem, and then submit a bug report along with the data in the clipping area below:
----Start cutting----
.................. (various characters)
----End Cut----
----Start the original---
.................. (All kinds of garbled)
In then, on a variety of Baidu, Google, Sougou ... No solution was found.
I remember when I used to build DZ station also encountered this problem. At that time, it is unintentional to import the random point of the code to select an item to import. But this is not workable, tangled. Again Baidu to see if there is similar repair software. Not found = =#. With notepad++ Open SQL look, no garbled, compare the SQL file can be imported. The high version can be imported, the low version should not be a problem, the format is correct. Follow the previous ideas on these uploaded files.
Try importing in local MySQL.
First change the name, upload a look. I found out that there was no mistake on the top.!!! However, there is a line of error (English is also lazy to translate).
Then re-compress the import ...!!! OK, local MySQL can be imported.
To import MySQL in the space.
Compressed SQL or a bug on top of the top bugs. I'll go... After decompression upload, only import more said table, plus a line of error prompts. It's too much of a pit to understand.
Simply Local has been imported complete, again from the local MySQL export, in the upload. Solve.
Summarize:
To see whether the database content is complete and garbled (if it is, basically hopeless = =).
Local build phpMyAdmin try to import (I'm using the Phpstudy green version)
In the then various mainstream, non-mainstream ideas. (Encoding conversion, version comparison, format comparison ...) ）
(I was changed file name after compression local MySQL, and then exported locally, in the import to space, looks like a luck ingredient, hehe.) ）
Baidu said, you can use the MySQL with the Repair tool, try to repair under. My database format and content are complete, and too lazy to install, there is no attempt!
Ps: There is no need to phpmyadmin to back up. = =

Note the following:
necessary knowledge:
MySQL code:
installation directory in MySQL, such as:
E:\Program files\mysql\mysql Server 5.0\ My.ini
can find the encoding of the MySQL library, most of which can be set to Uft-8:
Default-character-set=utf8
or GBK:
DEFAULT-CHARACTER-SET=GBK The
encoding is incorrect and can cause import to fail. The database will not take effect until the encoding is modified.
1. Condition: On the same server,
the MySQL database can be exported using the platform's export function normal backup and restore.
2. Conditions: On different servers, in the case of My.ini encoding, the
MySQL database can be exported using the platform of the export function normal backup and restore.
2. Conditions: Different servers, in the case of inconsistent My.ini encoding, the
must modify My.ini to become a consistent encoding, the MySQL database can use the platform to export the function of the normal backup and restore.
3. For files imported with phpMyAdmin or other tools, you will need to process them again before you can use the platform's import function:
Take phpMyAdmin as an example, after exporting, save the generated SQL statement as a. sql file, and then modify it with Notepad:
(1) Find this line at the beginning of create database such as:
CREATE db ' name ' DEFAULT CHARACTER SET latin1 COLLATE latin1_swedish_ci;
Precede--character , cancel the run of this line (because imports are imported with a normal user perspective and not allowed to be established)
This will make it possible to import with the platform's import functionality.
(2) Then, you can see if the encoding of the library is consistent with your server
if the encoding is inconsistent,
<1> either use Phpmymyadmin to back up the encoded. sql file to import. phpMyAdmin Landing on the home page can be selected for the code
<2> either modify the encoding in My.ini and restart MySQL to import (restart MySQL in the server, management tools, service management, restart), this way a higher chance of success, This is recommended.

First, database export
in general, the database is exported for backup or for database relocation. Then we typically choose SQL or Excel when exporting, rather than word,pdf. Select the table or all tables to export when you export. When choosing options, be aware that there are no necessary options, and if you choose other options, you may have trouble or errors in storing the database. So what do you choose?
in the fabric options (structure) option, we typically use the ADD if not exists,add auto_increment  value,enclose table and field names with Backquo TES (translated into Chinese characters as appropriate), that is, in the front of the options box tick (you will not tell me this you do not), in the Data option to select Complete inserts,extended inserts,use hexadecimal For Blob,export type is insert, of course if you are in order to update or replace you can choose Update or Replace. When the Save as file is ticked, it is automatically saved as a file (recommended), and then press go so that the database is stored in zip,gzip or bzip format.
Second, database import
    in particular, I built an empty database (without a table) with the same name as the exported database in the import of the database before I could import it, or I would often make an error. Set up the database and click on the corresponding database to enter (of course, in the phpMyAdmin environment), then we click on Import button, forget to say, if you choose to compress the export results, it is best to extract into a file form, although phpMyAdmin said that can identify compressed files ( Imported file compression will is automatically detected from: None, gzip, zip), in fact, is still not recognized:<), otherwise, phpMyAdmin will tell you that you found bugs (really bugs), the character set selection is the same as when you export, the default UTF8, and then click Go or execute OK, so that the database is moved to another place, but also convenient for you to move the station.