Mysql Dump Question...regarding gigantic file

[nyc03]

Hello. I am trying to recover a database for a 118 mb file for a client

I tried phpmyadmin and saw there were 10,000 + rows and the browser crashed trying to display them

so I attempted to do a mysql dump, and it just pauses in the command line, and the file grew to 200+ mb

How long should it take to do the dump? IT was growing to 200+ mb before I shut out of telnet. I felt it would not stop growing lol

Or is it possible that it CAN be 200+ mb and I should NOT worry?

When I waited 3 minutes and saw mysql did not confirm it was done, I got a bit spooked

What should I do? And is there a way to conserve memory when I do the dump?

[Owen]

Look in phpmyadmin... there's an option to show how big the database is... that's how big the backup file will be (more or less). I have a 1 gig database... it's a hassle to work w/ the backup files which are not conincidentally 1 gig. Nothing much you can do about it.

Owen

[Icheb]

It's usually smaller due to the indexes. Our forum's database is currently 161 mb big and the backup is about 115 mb.

[SubKamran]

I would use a software to dump, since there's no timeout (downloading is fine, but the backup part is the problem).

I'd go with http://www.mysqlstudio.com/ I'm buying their software, it's excellent.

[Technosailor]

nyc, if you need help, give me a shout. I can do that for you in a few mins.