Re: mysqldump specific tables from multiple databases?

2005-03-01 Thread Gleb Paharenko
Hello.



is it possible to mysqldump specific tables from multiple databases in

a single run?



No.



 database.  I can not (even off hours) lock the entire database (main

 one) long enough to do a full dump with locks so I see my options as:



You may write your own sql file in which you're locking the tables

which you need, selecting the data into outfiles and then unlocking 

the tables.









Sid Lane [EMAIL PROTECTED] wrote:

 all,

 

 is it possible to mysqldump specific tables from multiple databases in

 a single run?

 

 what I am trying to do is get replication slaves to a starting point

 but am somewhat challenged by the nature of our architecture. 

 specifically, we have a large number of relatively-static (updated

 only a few times/yr w/plenty of advance notice) tables which are

 relatively big (~50GB among them) and a small number of tables that

 are relatively small (~1GB among them) but are updated continuously

 (several million DMLs/day).  what I had done w/a single DB was

 dump/load the static tables to a new slave then dump/load the dynamic

 ones w/a --master-data which took ~1 min (acceptable off hours).  that

 got me to a point I could do a change master... then slave start and

 be in business.  I am now trying to merge in a small, secondary

 application (only ~50K DMLs/day) which is currently in a separate

 database.  I can not (even off hours) lock the entire database (main

 one) long enough to do a full dump with locks so I see my options as:

 

 1.  hope someone here knows how to do my original question

 2.  get architecture to sign off on consolidating tables into a single

 database (in progress).

 3.  hope someone here know an approach I hadn't even thought of

 (paradigm shifting w/o a clutch).

 

 thoughts?

 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   ___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



mysqldump specific tables from multiple databases?

2005-02-28 Thread Sid Lane
all,

is it possible to mysqldump specific tables from multiple databases in
a single run?

what I am trying to do is get replication slaves to a starting point
but am somewhat challenged by the nature of our architecture. 
specifically, we have a large number of relatively-static (updated
only a few times/yr w/plenty of advance notice) tables which are
relatively big (~50GB among them) and a small number of tables that
are relatively small (~1GB among them) but are updated continuously
(several million DMLs/day).  what I had done w/a single DB was
dump/load the static tables to a new slave then dump/load the dynamic
ones w/a --master-data which took ~1 min (acceptable off hours).  that
got me to a point I could do a change master... then slave start and
be in business.  I am now trying to merge in a small, secondary
application (only ~50K DMLs/day) which is currently in a separate
database.  I can not (even off hours) lock the entire database (main
one) long enough to do a full dump with locks so I see my options as:

1.  hope someone here knows how to do my original question
2.  get architecture to sign off on consolidating tables into a single
database (in progress).
3.  hope someone here know an approach I hadn't even thought of
(paradigm shifting w/o a clutch).

thoughts?

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]