Hi Jun, 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)
on source database: select * into '/full/path/to/your/output/file' from tablename; on target database: load data from '/full/path/of/file' into tablename .....; loading this way is much faster than using the output of mysqldump. Better also to recreate your indexes after you load data. Re your question below, try to do a SHOW PROCESSLIST after restarting and when you experience a slowdown and compare the outputs. hth, Johann On 12/22/06, Jun Martin <[EMAIL PROTECTED]> wrote:
Thanks, Michael. Now can you tell me why selecting data from a few tables in a mysql database (being used daily by tellers posting payments and new bills getting posted by the thousands daily) usually takes 20 minutes but takes only 4 minutes when the mysql service has been restarted less than one (1) day prior to the query? Michael Tinsay wrote: > man mysqldump > > ----- Original Message ---- > Oh, to be on topic, may I ask for suggestions on how BEST (fastest and > safest) to migrate mysql data from version 4.0 to 5.0? _________________________________________________ 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
-- For your web and software systems solution requirements: Sagada Solutions Corporation (www.sagadasolutions.com )
_________________________________________________ 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
