Sourcing a database backup while shopping ?

[Huppy]

I was just curious, about the length of time it's supposed to take to source
in a backed up database (324 mb in size).
At first I logged in to sql, using cmd and after typing "use peq", I typed in
"source peqbackup.sql" (without quotes). It started sourcing, with no
apparent errors, but just kept running and streaming "Query OK, 1 row
affected" up the window. It ran for over an hour, before I stopped it.
Then I cleared the sql peq, and ran the backup from Navicat using the
"execute sql". Although its still running as I type this, I left the house and
went shopping after I got the sourcing going, it was showing 5% done when
I returned, now at 6%, and there is no errors coming up.
Is this normal ? lol

[Huppy]

Guess I better add, that the puter I am using is not a slow one, lol
(3.2 Ghz 6-core, with 8 gigs of ram) Win 7 - 64bit

[Zandig]

Use SQLyog community:
http://code.google.com/p/sqlyog/downloads/list

Much better than Navicat which is known to cause issues. I seen Navicat cause problems when sourcing files for other emulators (i.e. WOW'sTrinitycore) and SQLyog works just fine.

[Huppy]

Use SQLyog community:
http://code.google.com/p/sqlyog/downloads/list

Much better than Navicat which is known to cause issues. I seen Navicat cause problems when sourcing files for other emulators (i.e. WOW'sTrinitycore) and SQLyog works just fine.

Ok, thank you, I will give that a try.

[Huppy]

Use SQLyog community:
http://code.google.com/p/sqlyog/downloads/list

Much better than Navicat which is known to cause issues. I seen Navicat cause problems when sourcing files for other emulators (i.e. WOW'sTrinitycore) and SQLyog works just fine.

Hey Zandig, I tried out that SQLyog and it works a hell of lot better, lol.
I backed up the db with it and sourced it in on another puter, just to
see how it would go and its awesome. Even the backup sql is a normal
size (148 mb) compared to the 324 mb that Navicat produced.
I even sourced the backup in using dos, or cmd as we call it now,
through mysql. only took 3 minutes. Thanks again for the info :)

[Akkadius]

Hey Zandig, I tried out that SQLyog and it works a hell of lot better, lol.
I backed up the db with it and sourced it in on another puter, just to
see how it would go and its awesome. Even the backup sql is a normal
size (148 mb) compared to the 324 mb that Navicat produced.
I even sourced the backup in using dos, or cmd as we call it now,
through mysql. only took 3 minutes. Thanks again for the info :)

mysqldump -uusername -ppassword databasename

Will dump it into the directory in which you run the command from in prompt. Or you could run it this way

mysqldump -uusername -ppassword databasename > "c:\Directory\To\Dump\to\database.sql"

[Huppy]

mysqldump -uusername -ppassword databasename

Will dump it into the directory in which you run the command from in prompt. Or you could run it this way

mysqldump -uusername -ppassword databasename > "c:\Directory\To\Dump\to\database.sql"

I actually tried that first string, once before, but your second suggestion
worked like a charm and took less than 30 seconds.
I miss the good old days of working with dos. Things went faster, lol

[Akkadius]

I actually tried that first string, once before, but your second suggestion
worked like a charm and took less than 30 seconds.
I miss the good old days of working with dos. Things went faster, lol

Sources very fast as well.

[Zandig]

Hey Zandig, I tried out that SQLyog and it works a hell of lot better, lol.
I backed up the db with it and sourced it in on another puter, just to
see how it would go and its awesome. Even the backup sql is a normal
size (148 mb) compared to the 324 mb that Navicat produced.
I even sourced the backup in using dos, or cmd as we call it now,
through mysql. only took 3 minutes. Thanks again for the info :)

Glad to hear it worked out for you.

SQLyog is a nice program to work with any aspect of your database.
More proof Navicat is much inferior and broken :D