mysqlimport with parallel threads is worth giving a try. It is similar
to 'load data infile' but with concurrent threads loading the tables.
I think , it was added in mysql-5.1.18. But it is said to work with
previous versions also according to the author :
http://krow.livejournal.com/519655
Shure, load data is way faster than full inserts.
I was thinking:
while $warnings -lt 100%
do
dump ora-data | mysql database
done
swap IP-addr.
On Mon, July 23, 2007 19:59, B. Keith Murphy wrote:
> I think you will find the load data infile will work faster. I am performing
> testing right
On 7/23/07, mos <[EMAIL PROTECTED]> wrote:
Load data will of course be much faster. However to obtain the maximum
speed you need to load the data to an empty table, because then MySQL will
load the data without updating the index for every row that's added, and
will instead rebuild the index only
At 11:44 AM 7/23/2007, Sid Lane wrote:
all,
I need to migrate ~12GB of data from an Oracle 10 database to a MySQL
5.0one in as short a window as practically possible (throw tablespace
in r/o,
migrate data & repoint web servers - every minute counts).
the two approaches I am considering are:
1.
I think you will find the load data infile will work faster. I am performing
testing right now in preparation for a migration from 4.1 to 5.0 but I am
confident that will be the case.
Keith
- Original Message -
From: "Sid Lane" < [EMAIL PROTECTED] >
To: mysql@lists.mysql.com
Sent: M
On 7/23/07, Sid Lane <[EMAIL PROTECTED]> wrote:
is either one significantly faster than the other?
Yes, LOAD DATA INFILE is much faster.
are there additional (faster) approaches I have not thought of?
Not that I've found. I think you'd have to write directly to the C
API to beat LOAD DATA
