Johann Tagle wrote:
Alternative to mysqldump, (since it is actually slow since an insert
statement is formed for every row on a table), take a look at the
SELECT INTO and LOAD DATA syntax of MySQL. For big tables, I use
mysqldump just to get the SQL to create the tables and indexes then
execute something like (note, not sure of syntax)
Yes, that's actually what I prefer since it's faster than mysqldump. I
was only trying to find out if there was a faster way.
Better also to recreate your indexes after you load data.
Now this I didn't know. Hmmm... maybe I'll give this a try... Thanks.
Re your question below, try to do a SHOW PROCESSLIST after restarting
and when you experience a slowdown and compare the outputs.
Thanks, but everyday the same set of users log on. and the processlist
*is* being viewed BEFORE the data "transfer" (select ... into outfile...
from some tables) is started, to make sure that no one has actually
requested for a lengthy query.
Any other suggestions? :-)
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph
