I use navicate, how to put the database back into the other server inside Ah, the inside is also loaded with navicate
Reply to discussion (solution)
Not used navicate, it is a graphical tool, should have the import and export button, look for it.
Not used navicate, it is a graphical tool, should have the import and export button, look for it. Exported SQL text, men are garbled ah
With what software to open, see what the SQL text is encoded.
With what software to open, see what the SQL text is encoded. is UTF8 ah, txt Open is garbled, with UTF8 Open is also garbled
Locate the location of the Navicate database and copy it to the appropriate location on the server.
Locate the location of the Navicate database and copy it to the appropriate location on the server. How can I find this?
Find the location of the Navicate database, and then copy one to the corresponding location on the server can be found, directly to another server in the same location is OK?
Post the parts you think are garbled, open with notepad++, change the character set to see.
Post the parts you think are garbled, open with notepad++, change the character set to see. It's right to open it with Notepad.
Locate the location of the Navicate database and copy it to the appropriate location on the server. How can I find this?
Yes, just copy the corresponding database location to the server.
Copy, but Open navicat doesn't show that database.
In the Navicat, there's a refresh.
If not, you may find the wrong position.
Take a look at the path sticker
Newly installed MySQL, only MySQL and test files two database, the red box is circled in the one I want to copy, but no refresh
Path Yes, if not, you can use the navicat inside the tool to export, and then import into the server
Path right Ah, if not, you can use the navicat inside the tool to export, and then import into the server is how the guide is garbled ... Can you add me to QQ remote a bit? 631373000
If not, just use phpMyAdmin to export the import.
Everywhere SQL files are imported into SQL file on another server.
It is garbled, it may be the result of the code is not unified
If the code is not uniform, it is possible that you built the database code and your import data encoding is not unified caused by,
It is recommended that you create a new database, unify the encoding into the data encoding you want to import, and then import it again to see
This is the original database encoding, I exported the SQL file, import into the new database in the same way no reaction ah
Post the parts you think are garbled, open with notepad++, change the character set to see. It's right to open it with Notepad.
In the correct case, save the file as. SQL and import it to see the downside.
If the import is not, you can use the query to import, that is, slower
Server-side Telnet your database ~ ~ Re-export the database ~ ~ Re-Import
Observe the topic discussion
If not, just use phpMyAdmin to export the import.
+ + + This tool is not very useful
The export import function inside is also good
Direct export well, it's all right.
Server-side Telnet your database ~ ~ Re-export the database ~ ~ Re-Import
I use navicate, how to put the database back into the other server inside Ah, the inside is also loaded with navicate
Navicat is a very useful tool.
In particular, the "data transfer" function, the most convenient between different databases to copy/backup.
Two cases:
1. You can connect to a database on two servers with Navicat, then use the data transfer function directly
For example, Xiudou and localhost two servers can be connected to a
2.navicat cannot access up to two servers at a time
Then first use the Navicat on the original database point right-click "Dump SQL File" to get the SQL file
Try to replicate it to another server.
Then open the Navicat on another server open the database connection, create the database (empty), then right-click, run the SQL file
The Better Way is:
1. Use the MySQL built-in mysqldump tool to export:
x:\mysql\bin\mysqldump-u[database user]-p[password]--opt--default-character-set=[database encoding, General UTF8]-R [database name] > [exported filename].sql
2. After exporting, go to MySQL and create a new database:
mysql> CREATE DATABASE [new name];
3. Finally, the exported SQL file is imported into the database again:
x:\mysql\bin\mysql-u[database user]-p[password]--default-character-set=[database encoding, General UTF8] [new database name] < [exported filename].sql