dumping mysql tables with mysqldump.exe

Question

0.00/5 (No votes)

See more:

hello everyone..

i want to take backup of mysql database programitically using c#. i went through lot of examples all are working fine..
there is an option in mysql workbench to dump the selected databases and restore the same. when i compare dumps from workbench and dump from my app (using mysqldump.exe and process class), i found out both are different.. my app generates dump as one file for one database and the same cannot be restored using mysql.exe and workbench. but dump from workbench is well defined and it can be restored in any instance.

my question is how to generate dump files as generated in mysql workbench..??

thanks

Posted 2-Dec-14 21:13pm

vikaskallidantheyil

Add a Solution

Comments

Garth J Lancaster 3-Dec-14 3:36am

I would have thought the parameters MySQLWorkbench passes to mysqldump would be in its setup/config somewhere ? (and yet, a quick google doesn't seem to find them) - there's also apparently a bundled version of mysqldump that it can use if you don't point it at a different version. There is a last resort way of finding out what parameters are used, a little messy .... fire up c# or c++, create a program called mysqldump that dumps all the command line its given to a file - point mysqlworkbench at the 'dummy' mysqldump and run it (don't forget to point it back) .. but there must be an easier way, surely

vikaskallidantheyil 4-Dec-14 4:31am

sorry garth ..i didnt understand wat u told regarding writing a programmme to dump. can u please elaborate..

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)